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 the next RFC.
>
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 functional
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
>> only need to copy the descriptor, not the a
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 address family called AF_XDP that is
>>> optimized for high performance packet processing a
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 processing and, in upcoming
>> patch sets, zero-copy semantics. In this
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 v2 version, we have removed
> all zero-copy rel
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 performance packet processing and, in upcoming
> >> patch set
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 version, we have removed
>> all zero-copy relat
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 smaller, simpler and
> h
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, simpler and
hopefully mor
10 matches
Mail list logo
