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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxKPXdYjwPnpq95V@mini-arch>
Date: Fri, 18 Oct 2024 09:39:57 -0700
From: Stanislav Fomichev <stfomichev@...il.com>
To: Muyang Tian <tianmuyang@...wei.com>
Cc: bpf@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Donald Hunter <donald.hunter@...il.com>,
	Björn Töpel <bjorn@...nel.org>,
	Magnus Karlsson <magnus.karlsson@...el.com>,
	Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
	Jonathan Lemon <jonathan.lemon@...il.com>,
	Alexei Starovoitov <ast@...nel.org>,
	Daniel Borkmann <daniel@...earbox.net>,
	Jesper Dangaard Brouer <hawk@...nel.org>,
	John Fastabend <john.fastabend@...il.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	yanan@...wei.com, xiesongyang@...wei.com, wuchangye@...wei.com,
	liuxin350@...wei.com, zhangmingyi5@...wei.com, liwei883@...wei.com,
	willemb@...gle.com
Subject: Re: [PATCH bpf-next v2 0/3] XDP metadata: Rx checksum/GSO hint; Tx
 GSO offload

On 10/18, Muyang Tian wrote:
> This series introduce XDP metadata functionality, including Rx checksum/GSO hint
> and Tx GSO offload. This is aimed to transfer control fields when processing jumbo
> frames between VMs.

Ideally, the series should also have the implementation of these hints
for a couple of devices and appropriate selftest updates to exercise
them.

For GSO, CC Willem going forward (I don't think I understand why
we want to have gso_type in the TX hint; something like header_len
seems like a better fit).

Please also don't post v3 yet and allow at least a week for the initial
reviewers to catch up..

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ