From: Matteo Croce <technoboy85@gmail.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v2 0/2] e1000e: add XDP support
Date: Thu, 12 Mar 2026 19:38:15 +0100 [thread overview]
Message-ID: <20260312183817.104878-1-teknoraver@meta.com> (raw)
Add XDP support to e1000e driver. First patch adds basic XDP support,
while the second one adds support for AF_XDP.
Tested on an Intel 82574L Gigabit card.
v2: added a missing 'select PAGE_POOL' which triggered a build failure
with some configurations.
Matteo Croce (2):
e1000e: add basic XDP support
e1000e: add XDP_REDIRECT support
drivers/net/ethernet/intel/Kconfig | 1 +
drivers/net/ethernet/intel/e1000e/e1000.h | 18 +-
drivers/net/ethernet/intel/e1000e/netdev.c | 600 +-
.../net/ethernet/intel/e1000e/netdev.c.orig | 8529 +++++++++++++++++
.../net/ethernet/intel/e1000e/netdev.c.rej | 46 +
5 files changed, 9182 insertions(+), 12 deletions(-)
create mode 100644 drivers/net/ethernet/intel/e1000e/netdev.c.orig
create mode 100644 drivers/net/ethernet/intel/e1000e/netdev.c.rej
--
2.53.0
next reply other threads:[~2026-03-12 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:38 Matteo Croce [this message]
2026-03-12 18:38 ` [PATCH net-next v2 1/2] e1000e: add basic XDP support Matteo Croce
2026-03-13 0:30 ` Jakub Kicinski
2026-03-13 1:15 ` Matteo Croce
2026-03-12 18:38 ` [PATCH net-next v2 2/2] e1000e: add XDP_REDIRECT support Matteo Croce
2026-03-13 13:16 ` [PATCH net-next v2 0/2] e1000e: add XDP support Kohei Enju
2026-03-13 14:19 ` Matteo Croce
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=20260312183817.104878-1-teknoraver@meta.com \
--to=technoboy85@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--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