From: Jakub Kicinski <kuba@kernel.org>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: Joe Damato <jdamato@fastly.com>,
magnus.karlsson@intel.com, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tsnep: Link queues to NAPIs
Date: Tue, 14 Jan 2025 13:22:26 -0800 [thread overview]
Message-ID: <20250114132226.3f0fdc31@kernel.org> (raw)
In-Reply-To: <fa737740-7cd0-4109-8712-09f2cb8dbef0@engleder-embedded.com>
On Tue, 14 Jan 2025 21:58:24 +0100 Gerhard Engleder wrote:
> > XDP and AF_XDP are different things. The XDP part of AF_XDP is to some
> > extent for advertising purposes :) If memory serves me well:
> >
> > XDP Tx -> these are additional queues automatically allocated for
> > in-kernel XDP, allocated when XDP is attached on Rx.
> > These should _not_ be listed in netlink queue, or NAPI;
> > IOW should not be linked to NAPI instances.
> > XDP Rx -> is not a thing, XDP attaches to stack queues, there are no
> > dedicated XDP Rx queues
> > AF_XDP -> AF_XDP "takes over" stack queues. It's a bit of a gray area.
> > I don't recall if we made a call on these being linked, but
> > they could probably be listed like devmem as a queue with
> > an extra attribute, not a completely separate queue type.
>
> For tsnep if have no additional XDP Tx queues, only the netdev queues
> are used. For AF_XDP/XSK I would keep the linking, as the stack queues
> still exist and are operated still with NAPI. Maybe queues taken over
> by AF_XDP/XSK get an extra attribute in the future. So I can keep the
> permanent linking to NAPI while interface is up no matter if XDP or
> AF_XDP/XSK is used or not. Did I understand it right?
I think so.
next prev parent reply other threads:[~2025-01-14 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 22:39 [PATCH net-next] tsnep: Link queues to NAPIs Gerhard Engleder
2025-01-13 12:24 ` Alexander Lobakin
2025-01-13 19:59 ` Joe Damato
2025-01-13 20:32 ` Gerhard Engleder
2025-01-13 21:48 ` Joe Damato
2025-01-13 21:56 ` Jakub Kicinski
2025-01-13 22:20 ` Joe Damato
2025-01-13 22:31 ` Jakub Kicinski
2025-01-13 22:36 ` Joe Damato
2025-01-14 20:58 ` Gerhard Engleder
2025-01-14 21:22 ` Jakub Kicinski [this message]
2025-01-14 23:00 ` patchwork-bot+netdevbpf
2025-01-14 23:05 ` 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=20250114132226.3f0fdc31@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=jdamato@fastly.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.