From: Jakub Kicinski <kuba@kernel.org>
To: Nelson Escobar <neescoba@cisco.com>
Cc: netdev@vger.kernel.org, satishkh@cisco.com, johndale@cisco.com
Subject: Re: [PATCH net-next 2/2] enic: Expand statistics gathering and reporting
Date: Mon, 26 Aug 2024 14:48:21 -0700 [thread overview]
Message-ID: <20240826144821.170f6019@kernel.org> (raw)
In-Reply-To: <20240823235401.29996-3-neescoba@cisco.com>
On Fri, 23 Aug 2024 16:54:01 -0700 Nelson Escobar wrote:
> Collect and report per rq/wq statistics in ethtool.
Take a look at:
https://docs.kernel.org/next/networking/netlink_spec/netdev.html#qstats
A lot of the stats you're trying to report should be reported via queue
stats. See struct netdev_stat_ops for more info.
--
pw-bot: cr
prev parent reply other threads:[~2024-08-26 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 23:53 [PATCH net-next 0/2] Expand statistics reported in ethtool Nelson Escobar
2024-08-23 23:54 ` [PATCH net-next 1/2] enic: Use macro instead of static const variables for array sizes Nelson Escobar
2024-08-23 23:54 ` [PATCH net-next 2/2] enic: Expand statistics gathering and reporting Nelson Escobar
2024-08-26 21:48 ` Jakub Kicinski [this message]
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=20240826144821.170f6019@kernel.org \
--to=kuba@kernel.org \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=satishkh@cisco.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).