From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH RFC v3 0/3] Thread safe
	rte_vhost_enqueue_burst().
Date: Fri, 18 Mar 2016 11:24:20 +0100
Message-ID: <1510934.ppYcvSL9Zy@xps13>
References: <1456314438-4021-1-git-send-email-i.maximets@samsung.com>
 <56EBD085.4030500@samsung.com>
 <C37D651A908B024F974696C65296B57B4C677AF2@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: "Xie, Huawei" <huawei.xie@intel.com>,
 Yuanhan Liu <yuanhan.liu@linux.intel.com>, dev@dpdk.org, "Richardson,
 Bruce" <bruce.richardson@intel.com>, Dyasly Sergey <s.dyasly@samsung.com>,
 Jerin Jacob <jerin.jacob@caviumnetworks.com>,
 Jianbo Liu <jianbo.liu@linaro.org>, Tetsuya Mukawa <mukawa@igel.co.jp>
To: Ilya Maximets <i.maximets@samsung.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51])
 by dpdk.org (Postfix) with ESMTP id 0ECB72C48
 for <dev@dpdk.org>; Fri, 18 Mar 2016 11:25:52 +0100 (CET)
Received: by mail-wm0-f51.google.com with SMTP id p65so61987550wmp.1
 for <dev@dpdk.org>; Fri, 18 Mar 2016 03:25:52 -0700 (PDT)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C677AF2@SHSMSX101.ccr.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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 many times discussed issue with barriers on arm.
> >
> > Best regards, Ilya Maximets.
> Right, for ARM. I put a comment there. Btw, could you add -in-reply-to
> when you send you next patch?

Please Ilya, send it alone when you'll have an ack from a vhost maintainer.