[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170822170913.35umf4j6hlmcnwtm@ast-mbp>
Date: Tue, 22 Aug 2017 10:09:15 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Jesper Dangaard Brouer <brouer@...hat.com>
Cc: "xdp-newbies@...r.kernel.org" <xdp-newbies@...r.kernel.org>,
John Fastabend <john.fastabend@...il.com>,
Daniel Borkmann <borkmann@...earbox.net>,
Andy Gospodarek <andy@...yhouse.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Paweł Staszewski <pstaszewski@...are.pl>
Subject: Re: XDP redirect measurements, gotchas and tracepoints
On Tue, Aug 22, 2017 at 08:37:10AM +0200, Jesper Dangaard Brouer wrote:
>
>
> > Once tx-ing netdev added to devmap we can enable xdp on it automatically?
>
> I think you are referring to Gotcha-2 here:
oops. yes :)
>
> Second gotcha(2): you cannot TX out a device, unless it also have a
> xdp bpf program attached. (This is an implicit dependency, as the
> driver code need to setup XDP resources before it can ndo_xdp_xmit).
>
> Yes, we should work on improving this situation. Auto enabling XDP
> when a netdev is added to a devmap is a good solution. Currently this
> is tied to loading an XDP bpf_prog. Do you propose loading a dummy
> bpf_prog on the netdev? (then we need to handle 1. not replacing
> existing bpf_prog, 2. on take-down don't remove "later" loaded
> bpf_prog).
right. these things need to be taken care of.
Technically for ndo_xdp_xmit to work the program doesn't need
to be attached, but the device needs to be in xdp mode with
configured xdp tx rings.
The easiest, of course, is just to document it :)
and may be add some sort of warning that if netdev is added
to devmap and it's not in xdp mode, return warning or error.
Powered by blists - more mailing lists