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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 4 Oct 2022 17:59:52 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Martin KaFai Lau <martin.lau@...ux.dev> Cc: Stanislav Fomichev <sdf@...gle.com>, Jesper Dangaard Brouer <jbrouer@...hat.com>, brouer@...hat.com, bpf@...r.kernel.org, netdev@...r.kernel.org, xdp-hints@...-project.net, larysa.zaremba@...el.com, memxor@...il.com, Lorenzo Bianconi <lorenzo@...nel.org>, mtahhan@...hat.com, Alexei Starovoitov <alexei.starovoitov@...il.com>, Daniel Borkmann <borkmann@...earbox.net>, Andrii Nakryiko <andrii.nakryiko@...il.com>, dave@...cker.co.uk, Magnus Karlsson <magnus.karlsson@...el.com>, bjorn@...nel.org Subject: Re: [PATCH RFCv2 bpf-next 00/18] XDP-hints: XDP gaining access to HW offload hints via BTF On Tue, 4 Oct 2022 17:25:51 -0700 Martin KaFai Lau wrote: > A intentionally wild question, what does it take for the driver to return the > hints. Is the rx_desc and rx_queue enough? When the xdp prog is calling a > kfunc/bpf-helper, like 'hwtstamp = bpf_xdp_get_hwtstamp()', can the driver > replace it with some inline bpf code (like how the inline code is generated for > the map_lookup helper). The xdp prog can then store the hwstamp in the meta > area in any layout it wants. Since you mentioned it... FWIW that was always my preference rather than the BTF magic :) The jited image would have to be per-driver like we do for BPF offload but that's easy to do from the technical perspective (I doubt many deployments bind the same prog to multiple HW devices)..
Powered by blists - more mailing lists