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
| ||
|
Date: Sun, 3 Apr 2016 00:02:22 -0700 From: Brenden Blanco <bblanco@...mgrid.com> To: Tom Herbert <tom@...bertland.com> Cc: "David S. Miller" <davem@...emloft.net>, Linux Kernel Network Developers <netdev@...r.kernel.org>, Alexei Starovoitov <alexei.starovoitov@...il.com>, ogerlitz@...lanox.com, Daniel Borkmann <daniel@...earbox.net>, john fastabend <john.fastabend@...il.com>, Jesper Dangaard Brouer <brouer@...hat.com> Subject: Re: [RFC PATCH 1/5] bpf: add PHYS_DEV prog type for early driver filter On Sat, Apr 02, 2016 at 12:39:45PM -0400, Tom Herbert wrote: > On Fri, Apr 1, 2016 at 9:21 PM, Brenden Blanco <bblanco@...mgrid.com> wrote: > > Add a new bpf prog type that is intended to run in early stages of the > > packet rx path. Only minimal packet metadata will be available, hence a new > > context type, struct xdp_metadata, is exposed to userspace. So far only > > expose the readable packet length, and only in read mode. > > > This would eventually be a generic abstraction of receive descriptors? Exactly. For instance, maybe let the hw's hash be available. > > > The PHYS_DEV name is chosen to represent that the program is meant only > > for physical adapters, rather than all netdevs. > > > Is there a hard restriction that this could only work with physical devices? I suppose not, but there wouldn't be much use case as compared to tc ingress, no? Since I was imagining that this new hook would be more restricted in functionality due to operating on descriptors rather than with a full skb, I tried to think of an appropriate name. If you think that this hook would spread, then a better name is needed. > [...]
Powered by blists - more mailing lists