> -Original Message-
> From: Eelco Chaudron
> Sent: Wednesday, May 31, 2023 7:14 PM
> To: Maxime Coquelin
> Cc: Xia, Chenbo ; david.march...@redhat.com;
> dev@dpdk.org
> Subject: Re: [PATCH v3 1/4] vhost: change vhost_virtqueue access lock to a
> read/write one
&
On 31 May 2023, at 11:27, Maxime Coquelin wrote:
> On 5/31/23 08:37, Xia, Chenbo wrote:
>> Hi Eelco,
>>
>>> -Original Message-
>>> From: Eelco Chaudron
>>> Sent: Wednesday, May 17, 2023 5:09 PM
>>> To: maxime.coque...@redhat.com; Xia, Chenbo ;
>>> david.march...@redhat.com
>>> Cc: dev@
On 5/31/23 08:37, Xia, Chenbo wrote:
Hi Eelco,
-Original Message-
From: Eelco Chaudron
Sent: Wednesday, May 17, 2023 5:09 PM
To: maxime.coque...@redhat.com; Xia, Chenbo ;
david.march...@redhat.com
Cc: dev@dpdk.org
Subject: [PATCH v3 1/4] vhost: change vhost_virtqueue access lock to
Hi Eelco,
> -Original Message-
> From: Eelco Chaudron
> Sent: Wednesday, May 17, 2023 5:09 PM
> To: maxime.coque...@redhat.com; Xia, Chenbo ;
> david.march...@redhat.com
> Cc: dev@dpdk.org
> Subject: [PATCH v3 1/4] vhost: change vhost_virtqueue access lock to a
> read/write one
>
> This
On 17 May 2023, at 19:33, Maxime Coquelin wrote:
> Hi Eelco,
>
> On 5/17/23 11:08, Eelco Chaudron wrote:
>> This change will allow the vhost interrupt datapath handling to be split
>> between two processed without one of them holding an explicit lock.
>>
>
> As I had a tuned PVP benchmarking se
Hi Eelco,
On 5/17/23 11:08, Eelco Chaudron wrote:
This change will allow the vhost interrupt datapath handling to be split
between two processed without one of them holding an explicit lock.
As I had a tuned PVP benchmarking setup at hand, I ran a 0.02% loss
RFC2544 test with and without this
6 matches
Mail list logo