[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1492033793.10587.73.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Wed, 12 Apr 2017 14:49:53 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
xdp-newbies@...r.kernel.org
Subject: Re: [PATCH v3 net-next RFC] Generic XDP
On Wed, 2017-04-12 at 14:30 -0700, Stephen Hemminger wrote:
> On Wed, 12 Apr 2017 14:54:15 -0400 (EDT)
> David Miller <davem@...emloft.net> wrote:
>
> > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> > index b0aa089..071a58b 100644
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -1891,9 +1891,17 @@ struct net_device {
> > struct lock_class_key *qdisc_tx_busylock;
> > struct lock_class_key *qdisc_running_key;
> > bool proto_down;
> > + struct bpf_prog __rcu *xdp_prog;
>
> It would be good if all devices could reuse this for the xdp_prog pointer.
> It would allow for could be used for introspection utility functions in future.
Problem is that some xdp usages were envisioning a per RX queue xdp
program.
Powered by blists - more mailing lists