From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
amritha.nambiar@intel.com, danielj@nvidia.com, mst@redhat.com,
michael.chan@broadcom.com, sdf@google.com,
przemyslaw.kitszel@intel.com, Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net
Subject: Re: [PATCH net-next v3 0/3] netdev: add per-queue statistics
Date: Thu, 7 Mar 2024 11:57:35 +0800 [thread overview]
Message-ID: <1709783855.0510879-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <20240306195509.1502746-1-kuba@kernel.org>
For series:
Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
On Wed, 6 Mar 2024 11:55:06 -0800, Jakub Kicinski <kuba@kernel.org> wrote:
> Hi!
>
> Per queue stats keep coming up, so it's about time someone laid
> the foundation. This series adds the uAPI, a handful of stats
> and a sample support for bnxt. It's not very comprehensive in
> terms of stat types or driver support. The expectation is that
> the support will grow organically. If we have the basic pieces
> in place it will be easy for reviewers to request new stats,
> or use of the API in place of ethtool -S.
>
> See patch 3 for sample output.
>
> v3:
> - remove the dump error handling, core does it now (b5a899154aa94)
> - fix ring mapping w/ XDP in bnxt
> v2: https://lore.kernel.org/all/20240229010221.2408413-1-kuba@kernel.org/
> - un-wrap short lines
> - s/stats/qstats/
> v1: https://lore.kernel.org/all/20240226211015.1244807-1-kuba@kernel.org/
> - rename projection -> scope
> - turn projection/scope into flags
> - remove the "netdev" scope since it's always implied
> rfc: https://lore.kernel.org/all/20240222223629.158254-1-kuba@kernel.org/
>
> Jakub Kicinski (3):
> netdev: add per-queue statistics
> netdev: add queue stat for alloc failures
> eth: bnxt: support per-queue statistics
>
> Documentation/netlink/specs/netdev.yaml | 91 +++++++++
> Documentation/networking/statistics.rst | 15 ++
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 65 +++++++
> include/linux/netdevice.h | 3 +
> include/net/netdev_queues.h | 56 ++++++
> include/uapi/linux/netdev.h | 20 ++
> net/core/netdev-genl-gen.c | 12 ++
> net/core/netdev-genl-gen.h | 2 +
> net/core/netdev-genl.c | 214 ++++++++++++++++++++++
> tools/include/uapi/linux/netdev.h | 20 ++
> 10 files changed, 498 insertions(+)
>
> --
> 2.44.0
>
>
next prev parent reply other threads:[~2024-03-07 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 19:55 [PATCH net-next v3 0/3] netdev: add per-queue statistics Jakub Kicinski
2024-03-06 19:55 ` [PATCH net-next v3 1/3] " Jakub Kicinski
2024-03-06 19:55 ` [PATCH net-next v3 2/3] netdev: add queue stat for alloc failures Jakub Kicinski
2024-03-06 19:55 ` [PATCH net-next v3 3/3] eth: bnxt: support per-queue statistics Jakub Kicinski
2024-03-06 21:57 ` Michael Chan
2024-03-07 3:57 ` Xuan Zhuo [this message]
2024-03-08 6:00 ` [PATCH net-next v3 0/3] netdev: add " patchwork-bot+netdevbpf
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=1709783855.0510879-1-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=amritha.nambiar@intel.com \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sdf@google.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).