From: Simon Horman <horms@kernel.org>
To: Nick Child <nnac123@linux.ibm.com>
Cc: netdev@vger.kernel.org, haren@linux.ibm.com, ricklind@us.ibm.com
Subject: Re: [PATCH net-next v2] ibmvnic: Add stat for tx direct vs tx batched
Date: Thu, 3 Oct 2024 15:41:55 +0100 [thread overview]
Message-ID: <20241003144155.GS1310185@kernel.org> (raw)
In-Reply-To: <20241001163531.1803152-1-nnac123@linux.ibm.com>
On Tue, Oct 01, 2024 at 11:35:31AM -0500, Nick Child wrote:
> Allow tracking of packets sent with send_subcrq direct vs
> indirect. `ethtool -S <dev>` will now provide a counter
> of the number of uses of each xmit method. This metric will
> be useful in performance debugging.
>
> Signed-off-by: Nick Child <nnac123@linux.ibm.com>
> ---
> Thanks Simon for review of v1 [1]
> Changes in v2:
> - move this patch to net-next instead of net
> 1 - https://lore.kernel.org/netdev/20240930175635.1670111-1-nnac123@linux.ibm.com/
Thanks for the update.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-10-03 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 16:35 [PATCH net-next v2] ibmvnic: Add stat for tx direct vs tx batched Nick Child
2024-10-03 14:41 ` Simon Horman [this message]
2024-10-04 0:40 ` 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=20241003144155.GS1310185@kernel.org \
--to=horms@kernel.org \
--cc=haren@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nnac123@linux.ibm.com \
--cc=ricklind@us.ibm.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).