From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Simon Horman <horms@kernel.org>
Cc: <intel-wired-lan@lists.osuosl.org>,
Michal Kubiak <michal.kubiak@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
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>,
<nxne.cnse.osdt.itp.upstreaming@intel.com>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH iwl-next v5 00/13] idpf: add XDP support
Date: Thu, 28 Aug 2025 17:17:10 +0200 [thread overview]
Message-ID: <593513fd-ffc6-44fc-9f53-59736e8fb514@intel.com> (raw)
In-Reply-To: <20250827172828.GP10519@horms.kernel.org>
From: Simon Horman <horms@kernel.org>
Date: Wed, 27 Aug 2025 18:28:28 +0100
> On Tue, Aug 26, 2025 at 05:54:54PM +0200, Alexander Lobakin wrote:
>> Add XDP support (w/o XSk for now) to the idpf driver using the libeth_xdp
>> sublib. All possible verdicts, .ndo_xdp_xmit(), multi-buffer etc. are here.
>> In general, nothing outstanding comparing to ice, except performance --
>> let's say, up to 2x for .ndo_xdp_xmit() on certain platforms and
>> scenarios.
>> idpf doesn't support VLAN Rx offload, so only the hash hint is
>> available for now.
>>
>> Patches 1-7 are prereqs, without which XDP would either not work at all or
>> work slower/worse/...
>
> Hi Alexander,
>
> I'm wondering if you could give a hash that this patch-set applies to.
> Or a branch where it has been applied.
>
> I suspect it's terribly obvious how to do this, but I'm drawing a blank here.
I could've left `base-commit-id`, but Tony does rebasing of his trees
every day, so this wouldn't help at all.
Moreover, it's to be applied to Tony's next-queue, but not on top of it,
because currently there are patches in the tree that will go *after* my
series to net-next. So it's a bit complicated.
>
> Thanks!
Thanks,
Olek
prev parent reply other threads:[~2025-08-28 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 15:54 [PATCH iwl-next v5 00/13] idpf: add XDP support Alexander Lobakin
2025-08-26 15:54 ` [PATCH iwl-next v5 01/13] xdp, libeth: make the xdp_init_buff() micro-optimization generic Alexander Lobakin
2025-08-26 15:54 ` [PATCH iwl-next v5 02/13] idpf: fix Rx descriptor ready check barrier in splitq Alexander Lobakin
2025-08-26 15:54 ` [PATCH iwl-next v5 03/13] idpf: use a saner limit for default number of queues to allocate Alexander Lobakin
2025-08-26 15:54 ` [PATCH iwl-next v5 04/13] idpf: link NAPIs to queues Alexander Lobakin
2025-08-26 15:54 ` [PATCH iwl-next v5 05/13] idpf: add 4-byte completion descriptor definition Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 06/13] idpf: remove SW marker handling from NAPI Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 07/13] idpf: add support for nointerrupt queues Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 08/13] idpf: prepare structures to support XDP Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 09/13] idpf: implement XDP_SETUP_PROG in ndo_bpf for splitq Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 10/13] idpf: use generic functions to build xdp_buff and skb Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 11/13] idpf: add support for XDP on Rx Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 12/13] idpf: add support for .ndo_xdp_xmit() Alexander Lobakin
2025-08-26 15:55 ` [PATCH iwl-next v5 13/13] idpf: add XDP RSS hash hint Alexander Lobakin
2025-08-27 17:28 ` [PATCH iwl-next v5 00/13] idpf: add XDP support Simon Horman
2025-08-27 20:42 ` Tony Nguyen
2025-08-28 15:17 ` Alexander Lobakin [this message]
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=593513fd-ffc6-44fc-9f53-59736e8fb514@intel.com \
--to=aleksander.lobakin@intel.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=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
--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).