From: Jakub Kicinski <kuba@kernel.org>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
virtualization@lists.linux.dev,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Tariq Toukan <tariqt@nvidia.com>,
Michael Chan <michael.chan@broadcom.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Shannon Nelson <shannon.nelson@amd.com>
Subject: Re: [PATCH net-next v3 3/6] virtio_net: support device stats
Date: Mon, 11 Mar 2024 08:43:30 -0700 [thread overview]
Message-ID: <20240311084330.47840d50@kernel.org> (raw)
In-Reply-To: <1710154125.7529383-1-xuanzhuo@linux.alibaba.com>
On Mon, 11 Mar 2024 18:48:45 +0800 Xuan Zhuo wrote:
> On Thu, 7 Mar 2024 08:50:21 -0800, Jakub Kicinski <kuba@kernel.org> wrote:
> > CC: Willem and some driver folks for more input, context: extending
> > https://lore.kernel.org/all/20240306195509.1502746-1-kuba@kernel.org/
> > to cover virtio stats.
> >
> > On Tue, 27 Feb 2024 16:03:00 +0800 Xuan Zhuo wrote:
> > > +static const struct virtnet_stat_desc virtnet_stats_rx_basic_desc[] = {
> > > + VIRTNET_STATS_DESC(rx, basic, packets),
> > > + VIRTNET_STATS_DESC(rx, basic, bytes),
> >
> > Covered.
>
> About "packets" and "bytes", here is coming from the hw device.
> Actually the driver also count "packets" and "bytes" in SW.
> So there are HW and SW versions. Do we need to distinguish them?
Yup, there are already separate counters defined for SW
and HW packets / bytes. For the feature specific counters
I don't think we need to have both SW and HW flavors defined.
But for pure rx / tx packets / bytes users may want to see both.
> > > +static const struct virtnet_stat_desc virtnet_stats_rx_gso_desc[] = {
> > > + VIRTNET_STATS_DESC(rx, gso, gso_packets),
> > > + VIRTNET_STATS_DESC(rx, gso, gso_bytes),
> >
> > I used the term "GSO" in conversations about Rx and it often confuses
> > people. Let's use "GRO", so hw-gro-packets, and hw-gro-bytes ?
> > Or maybe coalesce? "hw-rx-coalesce" ? That's quite a bit longer..
>
> GRO may also confuse people.
>
> I like hw-rx-coalesce-packets, hw-rx-coalesce-bytes.
FWIW the HW offload feature in ethtool -k is called 'rx-gro-hw',
but we can use "hw-rx-coalesce-*" and mention the feature in the
documentation.
next prev parent reply other threads:[~2024-03-11 15:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 8:02 [PATCH net-next v3 0/6] virtio-net: support device stats Xuan Zhuo
2024-02-27 8:02 ` [PATCH net-next v3 1/6] virtio_net: introduce device stats feature and structures Xuan Zhuo
2024-02-27 13:16 ` Jiri Pirko
2024-02-27 8:02 ` [PATCH net-next v3 2/6] virtio_net: virtnet_send_command supports command-specific-result Xuan Zhuo
2024-02-27 13:23 ` Jiri Pirko
2024-02-27 8:03 ` [PATCH net-next v3 3/6] virtio_net: support device stats Xuan Zhuo
2024-02-27 14:56 ` Jiri Pirko
2024-02-27 19:19 ` Simon Horman
2024-02-29 10:35 ` kernel test robot
2024-03-07 16:50 ` Jakub Kicinski
2024-03-11 10:48 ` Xuan Zhuo
2024-03-11 15:43 ` Jakub Kicinski [this message]
2024-02-27 8:03 ` [PATCH net-next v3 4/6] virtio_net: stats map include driver stats Xuan Zhuo
2024-02-27 15:05 ` Jiri Pirko
2024-02-27 8:03 ` [PATCH net-next v3 5/6] virtio_net: add the total stats field Xuan Zhuo
2024-02-27 14:54 ` Jakub Kicinski
2024-02-27 15:07 ` Jiri Pirko
2024-02-27 15:41 ` Jakub Kicinski
2024-02-27 15:59 ` Jiri Pirko
2024-03-07 9:36 ` Xuan Zhuo
2024-03-07 16:03 ` Jakub Kicinski
2024-02-27 8:03 ` [PATCH net-next v3 6/6] virtio_net: rename stat tx_timeout to timeout Xuan Zhuo
2024-02-27 15:08 ` Jiri Pirko
2024-02-27 13:14 ` [PATCH net-next v3 0/6] virtio-net: support device stats Jiri Pirko
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=20240311084330.47840d50@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=michael.chan@broadcom.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.com \
--cc=tariqt@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=willemdebruijn.kernel@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.