.com; zhihong.w...@intel.com;
>> tho...@monjalon.net; jer...@marvell.com; yinan.w...@intel.com;
>> Honnappa Nagarahalli ; Gavin Hu
>>
>> Cc: nd ; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v4 0/2] one way barrier for split vring idx
>>
>>
>>
>> On
yinan.w...@intel.com;
> Honnappa Nagarahalli ; Gavin Hu
>
> Cc: nd ; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 0/2] one way barrier for split vring idx
>
>
>
> On 4/29/20 7:45 PM, Ferruh Yigit wrote:
> > On 4/24/2020 4:39 AM, Joyce Kong wrote:
> >>
On 4/29/20 7:45 PM, Ferruh Yigit wrote:
> On 4/24/2020 4:39 AM, Joyce Kong wrote:
>> This patchset replaces the two-way barriers with C11 one-way barriers
>> for split vring idx, when the frontend and backend are implemented
>> in software.
>>
>> By doing PVP benchmarking, the test result of 2c1
On 4/24/2020 4:39 AM, Joyce Kong wrote:
> This patchset replaces the two-way barriers with C11 one-way barriers
> for split vring idx, when the frontend and backend are implemented
> in software.
>
> By doing PVP benchmarking, the test result of 2c1q showed the throughput
> increased 20% with the
On 4/24/20 5:39 AM, Joyce Kong wrote:
> This patchset replaces the two-way barriers with C11 one-way barriers
> for split vring idx, when the frontend and backend are implemented
> in software.
>
> By doing PVP benchmarking, the test result of 2c1q showed the throughput
> increased 20% with the
5 matches
Mail list logo