Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-12 Thread Björn Töpel
2018-04-11 20:43 GMT+02:00 Alexei Starovoitov : > On 4/11/18 5:17 AM, Björn Töpel wrote: >> >> >> In the current RFC you are required to create both an Rx and Tx >> queue to bind the socket, which is just weird for your "Rx on one >> device, Tx to another" scenario. I'll fix that in

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-11 Thread Alexei Starovoitov
On 4/11/18 5:17 AM, Björn Töpel wrote: In the current RFC you are required to create both an Rx and Tx queue to bind the socket, which is just weird for your "Rx on one device, Tx to another" scenario. I'll fix that in the next RFC. I would defer on adding new features until the key

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-11 Thread Björn Töpel
2018-04-10 16:14 GMT+02:00 William Tu : > On Mon, Apr 9, 2018 at 11:47 PM, Björn Töpel wrote: [...] >>> >> >> So you've setup two identical UMEMs? Then you can just forward the >> incoming Rx descriptor to the other netdev's Tx queue. Note, that you >>

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-10 Thread William Tu
On Mon, Apr 9, 2018 at 11:47 PM, Björn Töpel wrote: > 2018-04-09 23:51 GMT+02:00 William Tu : >> On Tue, Mar 27, 2018 at 9:59 AM, Björn Töpel wrote: >>> From: Björn Töpel >>> >>> This RFC introduces a new

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-10 Thread Björn Töpel
2018-04-09 23:51 GMT+02:00 William Tu : > On Tue, Mar 27, 2018 at 9:59 AM, Björn Töpel wrote: >> From: Björn Töpel >> >> This RFC introduces a new address family called AF_XDP that is >> optimized for high performance packet

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-04-09 Thread William Tu
On Tue, Mar 27, 2018 at 9:59 AM, Björn Töpel wrote: > From: Björn Töpel > > This RFC introduces a new address family called AF_XDP that is > optimized for high performance packet processing and, in upcoming > patch sets, zero-copy semantics. In this

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-03-29 Thread Jesper Dangaard Brouer
On Thu, 29 Mar 2018 08:16:23 +0200 Björn Töpel wrote: > 2018-03-28 23:18 GMT+02:00 Eric Leblond : > > Hello, > > > > On Tue, 2018-03-27 at 18:59 +0200, Björn Töpel wrote: > >> From: Björn Töpel > >> > >> > > optimized for high

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-03-29 Thread Björn Töpel
2018-03-28 23:18 GMT+02:00 Eric Leblond : > Hello, > > On Tue, 2018-03-27 at 18:59 +0200, Björn Töpel wrote: >> From: Björn Töpel >> >> > optimized for high performance packet processing and, in upcoming >> patch sets, zero-copy semantics. In this v2

Re: [RFC PATCH v2 00/14] Introducing AF_XDP support

2018-03-28 Thread Eric Leblond
Hello, On Tue, 2018-03-27 at 18:59 +0200, Björn Töpel wrote: > From: Björn Töpel > > optimized for high performance packet processing and, in upcoming > patch sets, zero-copy semantics. In this v2 version, we have removed > all zero-copy related code in order to make it

[RFC PATCH v2 00/14] Introducing AF_XDP support

2018-03-27 Thread Björn Töpel
From: Björn Töpel This RFC introduces a new address family called AF_XDP that is optimized for high performance packet processing and, in upcoming patch sets, zero-copy semantics. In this v2 version, we have removed all zero-copy related code in order to make it smaller,