From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, andrew+netdev@lunn.ch,
netdev@vger.kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
aleksander.lobakin@intel.com, sridhar.samudrala@intel.com,
emil.s.tantilov@intel.com, boolli@google.com, decot@google.com,
brianvv@google.com
Subject: [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2026-09-29 (idpf, libie)
Date: Tue, 29 Sep 2026 16:12:59 -0700 [thread overview]
Message-ID: <20260929231305.1515873-1-anthony.l.nguyen@intel.com> (raw)
Alexander Lobakin adds flow-based XDP fallback on idpf for firmware
without Tx FIFO support by tracking out-of-order descriptor completions;
the faster queue-based path is used when available.
Li Li improves virtchnl failure diagnostics in libie by logging
transaction details to aid in debugging.
The following are changes since commit 6e23f90f2b8c3ea3bf904f86f3ed06bf2844b4bc:
Merge branch 'net-consolidate-devmem-net_iov-freelist-and-dma-handling'
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 200GbE
Alexander Lobakin (1):
idpf: add flow-based XDP fallback for FWs without Tx FIFO support
Li Li (1):
libie: log more info when virtchnl fails
drivers/net/ethernet/intel/idpf/idpf.h | 2 +
drivers/net/ethernet/intel/idpf/idpf_txrx.c | 12 +-
drivers/net/ethernet/intel/idpf/idpf_txrx.h | 18 +--
drivers/net/ethernet/intel/idpf/xdp.c | 131 +++++++++++++++++++-
drivers/net/ethernet/intel/idpf/xdp.h | 73 ++++++++++-
drivers/net/ethernet/intel/libie/controlq.c | 11 ++
include/net/libeth/xdp.h | 13 ++
7 files changed, 241 insertions(+), 19 deletions(-)
--
2.47.1
next reply other threads:[~2026-09-29 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 23:12 Tony Nguyen [this message]
2026-09-29 23:13 ` [PATCH net-next 1/2] idpf: add flow-based XDP fallback for FWs without Tx FIFO support Tony Nguyen
[not found] ` <20260930231331.1E2051F000FF@smtp.kernel.org>
2026-10-01 15:43 ` Alexander Lobakin
2026-10-06 0:47 ` Jakub Kicinski
2026-10-03 23:35 ` netdev-bot+sashiko
2026-10-07 15:10 ` Alexander Lobakin
2026-09-29 23:13 ` [PATCH net-next 2/2] libie: log more info when virtchnl fails Tony Nguyen
2026-10-03 23:35 ` netdev-bot+sashiko
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=20260929231305.1515873-1-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=boolli@google.com \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@kernel.org \
--cc=emil.s.tantilov@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@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).