netdev - Re: [RFC net-next 2/2] eth: bnxt: add support rx side device memory TCP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250402154504.0da028d2@kernel.org>
Date: Wed, 2 Apr 2025 15:45:04 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mina Almasry <almasrymina@...gle.com>
Cc: Taehee Yoo <ap420073@...il.com>, davem@...emloft.net, pabeni@...hat.com,
 edumazet@...gle.com, andrew+netdev@...n.ch, horms@...nel.org,
 michael.chan@...adcom.com, pavan.chebbi@...adcom.com,
 ilias.apalodimas@...aro.org, dw@...idwei.uk, netdev@...r.kernel.org,
 kuniyu@...zon.com, sdf@...ichev.me, aleksander.lobakin@...el.com
Subject: Re: [RFC net-next 2/2] eth: bnxt: add support rx side device memory
 TCP

On Wed, 2 Apr 2025 15:11:39 -0700 Mina Almasry wrote:
> > We also shouldn't pass netmem to XDP init, it's strange conceptually.
> > If we reach XDP it has to be a non-net_iov page.
> 
> Very noob question, but is XDP/netmem interactions completely
> impossible for some reason? I was thinking XDP progs that only
> touch/need the header may work with unreadable netmem, and if we ever
> add readable net_iovs then those maybe can be exposed to XDP, no? Or
> am I completely off the rails here?

Right, I was referring to the current state of things.
Extensions both to XDP semantics or net_iov could change
the picture.