From: Jacob Keller <jacob.e.keller@intel.com>
To: <edward.cree@amd.com>, <linux-net-drivers@amd.com>,
<davem@davemloft.net>, <kuba@kernel.org>, <edumazet@google.com>,
<pabeni@redhat.com>
Cc: Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>,
<habetsm.xilinx@gmail.com>
Subject: Re: [PATCH v4 net-next 4/7] sfc: account XDP TXes in netdev base stats
Date: Fri, 4 Oct 2024 15:36:48 -0700 [thread overview]
Message-ID: <c18fe74f-392d-4edf-b343-ef955741fe67@intel.com> (raw)
In-Reply-To: <44d77cdcc1df6d2606945481ded02ba824d9d507.1727703521.git.ecree.xilinx@gmail.com>
On 9/30/2024 6:52 AM, edward.cree@amd.com wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> When we handle a TX completion for an XDP packet, it is not counted
> in the per-TXQ netdev stats. Record it in new internal counters,
> and include those in the device-wide total in efx_get_base_stats().
>
> Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
> ---Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-10-04 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 13:52 [PATCH v4 net-next 0/7] sfc: per-queue stats edward.cree
2024-09-30 13:52 ` [PATCH v4 net-next 1/7] sfc: remove obsolete counters from struct efx_channel edward.cree
2024-09-30 13:52 ` [PATCH v4 net-next 2/7] sfc: implement basic per-queue stats edward.cree
2024-10-04 22:36 ` Jacob Keller
2024-09-30 13:52 ` [PATCH v4 net-next 3/7] sfc: add n_rx_overlength to ethtool stats edward.cree
2024-09-30 13:52 ` [PATCH v4 net-next 4/7] sfc: account XDP TXes in netdev base stats edward.cree
2024-10-04 22:36 ` Jacob Keller [this message]
2024-09-30 13:52 ` [PATCH v4 net-next 5/7] sfc: implement per-queue rx drop and overrun stats edward.cree
2024-09-30 13:52 ` [PATCH v4 net-next 6/7] sfc: implement per-queue TSO (hw_gso) stats edward.cree
2024-09-30 13:52 ` [PATCH v4 net-next 7/7] sfc: add per-queue RX bytes stats edward.cree
2024-10-04 22:37 ` [PATCH v4 net-next 0/7] sfc: per-queue stats Jacob Keller
2024-10-06 15:10 ` 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=c18fe74f-392d-4edf-b343-ef955741fe67@intel.com \
--to=jacob.e.keller@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).