On 4/30/20 11:16 AM, Joyce Kong wrote:
>> -----Original Message-----
>> From: Maxime Coquelin <maxime.coque...@redhat.com>
>> Sent: Thursday, April 30, 2020 5:09 PM
>> To: Ferruh Yigit <ferruh.yi...@intel.com>; Joyce Kong
>> <joyce.k...@arm.com>; step...@networkplumber.org;
>> xiaolong...@intel.com; tiwei....@intel.com; zhihong.w...@intel.com;
>> tho...@monjalon.net; jer...@marvell.com; yinan.w...@intel.com;
>> Honnappa Nagarahalli <honnappa.nagaraha...@arm.com>; Gavin Hu
>> <gavin...@arm.com>
>> Cc: nd <n...@arm.com>; 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:
>>>> 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 0.001% of acceptable loss rate on
>>>> Thunderx2 platform.[1]
>>>>
>>>> By doing vhost-user + virtio-user case benchmarking, 4% performance
>>>> gain was measured on Thunderx2 platform by 2c1q RFC2544 test of
>>>> 0.001% loss, and 4.7% performance was improved on Dell platform by
>>>> 1c1q RFC2544 test of zero packet loss.[2]
>>>>
>>>> [1]https://doc.dpdk.org/guides/howto/pvp_reference_benchmark.html
>>>>
>> [2]https://doc.dpdk.org/dts/test_plans/pvp_multi_paths_performance_test
>> _plan.html
>>>> PVP test with virtio 1.0 normal path
>>>>
>>>> v4:
>>>> Remove some duplicated code comment.
>>>>
>>>> v3:
>>>> Modify some style error.
>>>>
>>>> v2:
>>>> Add test performance statistics.
>>>>
>>>> Joyce Kong (2):
>>>> virtio: one way barrier for split vring used idx
>>>> virtio: one way barrier for split vring avail idx
>>>>
>>>
>>> Hi Joyce,
>>>
>>> When 'CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_DUMP=y' enabled, build fails.
>> Can
>>> you please check it?
>>
>> Hi Joyce,
>>
>> I will need the fix today, just send a v5 for the series.
>> If not possible to do it today, please let me know.
>>
>> Maxime
>>
> Hi Maxime,
> I have just fixed the issue and sent out the v5, please have a review.
> Thanks.
Thanks! That was fast :)
Maxime
>>
>>> Thanks,
>>> ferruh
>>>
>
