From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: Joe Damato <jdamato@fastly.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
intel-wired-lan@lists.osuosl.org (moderated list:INTEL ETHERNET
DRIVERS), linux-kernel@vger.kernel.org (open list)
Subject: [net-next v3 0/2] e1000/e1000e: Link IRQs, NAPIs, and queues
Date: Mon, 30 Sep 2024 17:12:30 +0000 [thread overview]
Message-ID: <20240930171232.1668-1-jdamato@fastly.com> (raw)
Greetings:
Welcome to v3.
v1 was an RFC [1] for just e1000e, v2 was an RFC [2] for both e1000e and
e1000.
This series adds support for netdev-genl to e1000e and e1000.
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'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/T/
[2]: https://lore.kernel.org/lkml/20240925162937.2218-1-jdamato@fastly.com/
v3:
- No longer an RFC
- Updated commit messages
- No functional or code changes at all
rfcv2:
- Include patch for e1000
Joe Damato (2):
e1000e: Link NAPI instances to queues and IRQs
e1000: Link NAPI instances to queues and IRQs
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-30 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 17:12 Joe Damato [this message]
2024-09-30 17:12 ` [net-next v3 1/2] e1000e: Link NAPI instances to queues and IRQs Joe Damato
2024-10-01 10:50 ` Simon Horman
2024-10-08 13:45 ` [Intel-wired-lan] " Avigail Dahan
2024-09-30 17:12 ` [net-next v3 2/2] e1000: " Joe Damato
2024-10-01 10:50 ` Simon Horman
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=20240930171232.1668-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;
as well as URLs for NNTP newsgroup(s).