From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: haiyangz@microsoft.com, shradhagupta@linux.microsoft.com,
horms@kernel.org, Joe Damato <jdamato@fastly.com>,
"David S. Miller" <davem@davemloft.net>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Wei Liu <wei.liu@kernel.org>,
linux-hyperv@vger.kernel.org (open list:Hyper-V/Azure CORE AND
DRIVERS), linux-kernel@vger.kernel.org (open list)
Subject: [net-next v2 0/1] hyperv: Link queues to NAPIs
Date: Mon, 30 Sep 2024 17:27:08 +0000 [thread overview]
Message-ID: <20240930172709.57417-1-jdamato@fastly.com> (raw)
Greetings:
Welcome to v2.
This was previously an RFC [1], see changelog below.
I've only compile tested this series; I don't have the software for testing
this so I am hoping some one from Microsoft can review and test this
following the instructions below :)
This change allows users to query the mapping of queues to NAPIs using
the netdev-genl interface.
Once this patch has been applied, this can be tested using the cli included
in the kernel tree like this:
$ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
--dump queue-get --json='{"ifindex": 2}'
Substituting the ifindex above for the correct ifindex on your system
(which is, presumably, a hyper-V VM).
A sample of expected output would look like:
[{'id': 0, 'ifindex': 2, 'napi-id': 145, 'type': 'rx'},
{'id': 0, 'ifindex': 2, 'napi-id': 145, 'type': 'tx'}]
Which shows a mapping of queue ID (0) to NAPI ID (145) for both RX and TX
queues. Having this mapping is extremely useful for user apps for a variety
of use cases, including epoll-based busy poll which relies on the NAPI ID.
It would be really great to add support for this API to hyper-V so that
applications (including CI and automated testing facilities) could make use
of this API in VMs.
Sorry, I don't know much at all about hyper-V, but please let me know if
there is anything I can do to help.
Thanks,
Joe
[1]: https://lore.kernel.org/netdev/20240924234851.42348-1-jdamato@fastly.com/
v2:
- Added Haiyang Zhang's Reviewed-by
- Added Shradha Gupta's Tested-by
- Commit message updated to include test output from Shradha
- Wrapped lines to 80 characters, as suggested by Simon Horman (no
functional changes introduced)
Joe Damato (1):
hv_netvsc: Link queues to NAPIs
drivers/net/hyperv/netvsc.c | 13 ++++++++++++-
drivers/net/hyperv/rndis_filter.c | 9 +++++++--
2 files changed, 19 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-30 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 17:27 Joe Damato [this message]
2024-09-30 17:27 ` [net-next v2 1/1] hv_netvsc: Link queues to NAPIs Joe Damato
2024-10-06 15:30 ` [net-next v2 0/1] hyperv: " 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=20240930172709.57417-1-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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