From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: Daniel Jurgens <danielj@nvidia.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"abeni@redhat.com" <abeni@redhat.com>,
Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH net-next] virtio_net: Add TX stop and wake counters
Date: Thu, 1 Feb 2024 20:21:06 -0800 [thread overview]
Message-ID: <20240201202106.25d6dc93@kernel.org> (raw)
In-Reply-To: <CAL+tcoCsT6UJ=2zxL-=0n7sQ2vPC5ybnQk9bGhF6PexZN=-29Q@mail.gmail.com>
On Wed, 31 Jan 2024 10:54:33 +0800 Jason Xing wrote:
> > [danielj@sw-mtx-051 upstream]$ ethtool -S ens2f1np1 | grep 'stop\|wake'
> > tx_queue_stopped: 0
> > tx_queue_wake: 0
> > tx0_stopped: 0
> > tx0_wake: 0
> > ....
>
> Yes, that's it! What I know is that only mlx drivers have those two
> counters, but they are very useful when debugging some issues or
> tracking some historical changes if we want to.
Can you say more? I'm curious what's your use case.
next prev parent reply other threads:[~2024-02-02 4:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 14:25 [PATCH net-next] virtio_net: Add TX stop and wake counters Daniel Jurgens
2024-01-30 14:58 ` Michael S. Tsirkin
2024-01-30 15:40 ` Daniel Jurgens
2024-01-30 15:41 ` Michael S. Tsirkin
2024-01-30 15:50 ` Daniel Jurgens
2024-01-30 15:53 ` Michael S. Tsirkin
2024-01-30 17:33 ` Daniel Jurgens
2024-01-31 2:54 ` Jason Xing
2024-02-02 4:21 ` Jakub Kicinski [this message]
2024-02-02 6:52 ` Jason Xing
2024-02-02 16:01 ` Jakub Kicinski
2024-02-02 16:46 ` Daniel Jurgens
2024-02-02 17:38 ` Jakub Kicinski
2024-06-07 9:16 ` Jason Xing
2024-06-07 12:36 ` Dan Jurgens
2024-06-08 0:41 ` Jason Xing
2024-06-10 17:57 ` Jakub Kicinski
2024-06-11 2:05 ` Jason Xing
2024-02-04 1:20 ` Jason Wang
2024-02-04 12:39 ` Michael S. Tsirkin
2024-02-05 1:45 ` Jason Wang
2024-02-07 20:21 ` Michael S. Tsirkin
2024-02-07 19:38 ` Daniel Jurgens
2024-02-07 20:19 ` Michael S. Tsirkin
2024-02-07 20:59 ` Daniel Jurgens
2024-02-20 18:02 ` Dan Jurgens
2024-02-20 18:05 ` Michael S. Tsirkin
2024-02-20 22:27 ` Jakub Kicinski
2024-01-30 15:16 ` Heng Qi
2024-01-30 15:43 ` Daniel Jurgens
2024-01-30 15:52 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240201202106.25d6dc93@kernel.org \
--to=kuba@kernel.org \
--cc=abeni@redhat.com \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kerneljasonxing@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).