[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Yuanhan Liu
On Fri, Mar 18, 2016 at 10:34:56AM +0100, Thomas Monjalon wrote: > 2016-03-18 17:16, Yuanhan Liu: > > On Fri, Mar 18, 2016 at 09:09:04AM +0100, Thomas Monjalon wrote: > > > 2016-03-18 16:00, Yuanhan Liu: > > > > On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote: > > > > > 2016-02-24 1

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Yuanhan Liu
On Fri, Mar 18, 2016 at 09:09:04AM +0100, Thomas Monjalon wrote: > 2016-03-18 16:00, Yuanhan Liu: > > On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote: > > > 2016-02-24 14:47, Ilya Maximets: > > > > Implementation of rte_vhost_enqueue_burst() based on lockless > > > > ring-buffer >

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Yuanhan Liu
On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote: > 2016-02-24 14:47, Ilya Maximets: > > Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer > > algorithm and contains almost all to be thread-safe, but it's not. > > > > This set adds required changes. > > > >

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Ilya Maximets
On 18.03.2016 12:46, Yuanhan Liu wrote: > On Fri, Mar 18, 2016 at 10:34:56AM +0100, Thomas Monjalon wrote: >> 2016-03-18 17:16, Yuanhan Liu: >>> On Fri, Mar 18, 2016 at 09:09:04AM +0100, Thomas Monjalon wrote: 2016-03-18 16:00, Yuanhan Liu: > On Thu, Mar 17, 2016 at 04:29:32PM +0100, Tho

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Thomas Monjalon
2016-03-18 10:10, Xie, Huawei: > On 3/18/2016 5:55 PM, Ilya Maximets wrote: > > Hi all. > > And what about first patch of this series: > > "vhost: use SMP barriers instead of compiler ones." ? > > > > It's not about thread safety in terms of 'lockless'. It is the standalone > > patch that fixes man

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Thomas Monjalon
2016-03-18 17:16, Yuanhan Liu: > On Fri, Mar 18, 2016 at 09:09:04AM +0100, Thomas Monjalon wrote: > > 2016-03-18 16:00, Yuanhan Liu: > > > On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote: > > > > 2016-02-24 14:47, Ilya Maximets: > > > > > Implementation of rte_vhost_enqueue_burst()

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Xie, Huawei
On 3/18/2016 5:55 PM, Ilya Maximets wrote: > Hi all. > And what about first patch of this series: > "vhost: use SMP barriers instead of compiler ones." ? > > It's not about thread safety in terms of 'lockless'. It is the standalone > patch that fixes many times discussed issue with barriers on arm.

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-18 Thread Thomas Monjalon
2016-03-18 16:00, Yuanhan Liu: > On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote: > > 2016-02-24 14:47, Ilya Maximets: > > > Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer > > > algorithm and contains almost all to be thread-safe, but it's not. > > > > >

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-03-17 Thread Thomas Monjalon
2016-02-24 14:47, Ilya Maximets: > Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer > algorithm and contains almost all to be thread-safe, but it's not. > > This set adds required changes. > > First patch in set is a standalone patch that fixes many times discussed > issu

[dpdk-dev] [PATCH RFC v3 0/3] Thread safe rte_vhost_enqueue_burst().

2016-02-24 Thread Ilya Maximets
Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer algorithm and contains almost all to be thread-safe, but it's not. This set adds required changes. First patch in set is a standalone patch that fixes many times discussed issue with barriers on different architectures. Se