[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170412.215512.844254291088810993.davem@davemloft.net>
Date: Wed, 12 Apr 2017 21:55:12 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: stephen@...workplumber.org, netdev@...r.kernel.org,
xdp-newbies@...r.kernel.org
Subject: Re: [PATCH v3 net-next RFC] Generic XDP
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 12 Apr 2017 14:49:53 -0700
> 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.
True, but that hasn't materialized yet so designing for it so soon
doesn't make a lot of sense.
Powered by blists - more mailing lists