Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Tue, Jul 26, 2016 at 10:53 AM, John Fastabend wrote: > On 16-07-26 09:08 AM, Tom Herbert wrote: >> On Tue, Jul 26, 2016 at 6:31 AM, Thomas Monjalon >> wrote: >>> Hi, >>> >>> About RX filtering, there is an ongoing effort in DPDK to write an

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Tue, 12 Jul 2016 12:13:01 -0700, John Fastabend wrote: > On 16-07-11 07:24 PM, Alexei Starovoitov wrote: > > On Sat, Jul 09, 2016 at 01:27:26PM +0200, Jesper Dangaard Brouer wrote: > >> On Fri, 8 Jul 2016 18:51:07 +0100 > >> Jakub Kicinski wrote: > >> > >>> On

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On 16-07-11 07:24 PM, Alexei Starovoitov wrote: > On Sat, Jul 09, 2016 at 01:27:26PM +0200, Jesper Dangaard Brouer wrote: >> On Fri, 8 Jul 2016 18:51:07 +0100 >> Jakub Kicinski wrote: >> >>> On Fri, 8 Jul 2016 09:45:25 -0700, John Fastabend wrote: The only

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Sat, Jul 09, 2016 at 01:27:26PM +0200, Jesper Dangaard Brouer wrote: > On Fri, 8 Jul 2016 18:51:07 +0100 > Jakub Kicinski wrote: > > > On Fri, 8 Jul 2016 09:45:25 -0700, John Fastabend wrote: > > > The only distinction between VFs and queue groupings on my side

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Thu, 7 Jul 2016 19:22:12 -0700, Alexei Starovoitov wrote: > > If the goal is to just separate XDP traffic from non-XDP traffic you could > > accomplish this with a combination of SR-IOV/macvlan to separate the device > > queues into multiple netdevs and then run XDP on just one of the

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Thu, Jul 07, 2016 at 09:05:29PM -0700, John Fastabend wrote: > On 16-07-07 07:22 PM, Alexei Starovoitov wrote: > > On Thu, Jul 07, 2016 at 03:18:11PM +, Fastabend, John R wrote: > >> Hi Jesper, > >> > >> I have done some previous work on proprietary systems where we > >> used hardware to do

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On 16-07-07 07:22 PM, Alexei Starovoitov wrote: > On Thu, Jul 07, 2016 at 03:18:11PM +, Fastabend, John R wrote: >> Hi Jesper, >> >> I have done some previous work on proprietary systems where we >> used hardware to do the classification/parsing then passed a cookie to the >> software which

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Thu, Jul 07, 2016 at 03:18:11PM +, Fastabend, John R wrote: > Hi Jesper, > > I have done some previous work on proprietary systems where we used hardware > to do the classification/parsing then passed a cookie to the software which > used the cookie to lookup a program to run on the

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On 16-07-07 10:53 AM, Tom Herbert wrote: > On Thu, Jul 7, 2016 at 9:12 AM, Jakub Kicinski > wrote: >> On Thu, 7 Jul 2016 15:18:11 +, Fastabend, John R wrote: >>> The other interesting thing would be to do more than just packet >>> steering but actually run a more

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Thu, Jul 7, 2016 at 9:12 AM, Jakub Kicinski wrote: > On Thu, 7 Jul 2016 15:18:11 +, Fastabend, John R wrote: >> The other interesting thing would be to do more than just packet >> steering but actually run a more complete XDP program. Netronome >> supports

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

On Thu, 7 Jul 2016 15:18:11 +, Fastabend, John R wrote: > The other interesting thing would be to do more than just packet > steering but actually run a more complete XDP program. Netronome > supports this right. The question I have though is this a stacked of > XDP programs one or more

Re: [iovisor-dev] XDP seeking input from NIC hardware vendors

Hi Jesper, I have done some previous work on proprietary systems where we used hardware to do the classification/parsing then passed a cookie to the software which used the cookie to lookup a program to run on the packet. When your programs are structured as a bunch of parsing followed by some