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
| ||
|
Message-ID: <20190821113816.4dee030a@cakuba.netronome.com> Date: Wed, 21 Aug 2019 11:38:16 -0700 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: Toshiaki Makita <toshiaki.makita1@...il.com> Cc: Stanislav Fomichev <sdf@...ichev.me>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Martin KaFai Lau <kafai@...com>, Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>, "David S. Miller" <davem@...emloft.net>, Jesper Dangaard Brouer <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com>, Jamal Hadi Salim <jhs@...atatu.com>, Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org, bpf@...r.kernel.org, William Tu <u9012063@...il.com> Subject: Re: [RFC PATCH bpf-next 00/14] xdp_flow: Flow offload to XDP On Wed, 21 Aug 2019 17:49:33 +0900, Toshiaki Makita wrote: > > Having an implementation nor support a feature of another implementation > > and degrade gracefully to the slower one is not necessarily breakage. > > We need to make a concious decision here, hence the clarifying question. > > As I described above, breakage can happen in some case, and if the patch > breaks xdp_flow I think we need to fix xdp_flow at the same time. If > xdp_flow does not support newly added features but it works for existing > ones, it is OK. In the first place not all features can be offloaded to > xdp_flow. I think this is the same as HW-offload. I see, that sounds reasonable, yes. Thanks for clarifying.
Powered by blists - more mailing lists