From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Joe Damato <jdamato@fastly.com>,
open list <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: [Intel-wired-lan] [RFC v2 net-next 0/2] e1000/e1000e: Link IRQs, NAPIs, and queues
Date: Wed, 25 Sep 2024 16:29:35 +0000 [thread overview]
Message-ID: <20240925162937.2218-1-jdamato@fastly.com> (raw)
Greetings:
This RFC v2 follows from an RFC submission I sent [1] for e1000e. The
original RFC added netdev-genl support for e1000e, but this new RFC
includes a patch to add support for e1000, as well.
Supporting this API in these drivers is very useful as commonly used
virtualization software, like VMWare Fusion and VirtualBox, expose e1000e
and e1000 NICs to VMs.
Developers who work on user apps in VMs may find themselves in need of
access to this API to build, test, or run CI on their apps. This is
especially true for apps which use epoll based busy poll and rely on
userland mapping NAPI IDs to queues.
I plan to send this series as an official patch series next week when
net-next reopens, but wanted to give the Intel folks a head's up incase
they had any comments or feedback I could address before then.
I've tested both patches; please see the commit messages for more details.
Thanks,
Joe
[1]: https://lore.kernel.org/lkml/20240918135726.1330-1-jdamato@fastly.com/
rfcv2:
- Added patch 2 which includes netdev-genl support for e1000
Joe Damato (2):
e1000e: link NAPI instances to queues and IRQs
e1000: Link IRQs and queues to NAPIs
drivers/net/ethernet/intel/e1000/e1000_main.c | 5 +++++
drivers/net/ethernet/intel/e1000e/netdev.c | 11 +++++++++++
2 files changed, 16 insertions(+)
--
2.34.1
next reply other threads:[~2024-09-25 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:29 Joe Damato [this message]
2024-09-25 16:29 ` [Intel-wired-lan] [RFC v2 net-next 1/2] e1000e: link NAPI instances to queues and IRQs Joe Damato
2024-09-25 16:29 ` [Intel-wired-lan] [RFC v2 net-next 2/2] e1000: Link IRQs and queues to NAPIs Joe Damato
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=20240925162937.2218-1-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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