From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <huawei.xie@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 334ED5947
 for <dev@dpdk.org>; Fri, 18 Mar 2016 11:10:45 +0100 (CET)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by fmsmga104.fm.intel.com with ESMTP; 18 Mar 2016 03:10:44 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.24,354,1455004800"; d="scan'208";a="913802375"
Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206])
 by orsmga001.jf.intel.com with ESMTP; 18 Mar 2016 03:10:43 -0700
Received: from fmsmsx158.amr.corp.intel.com (10.18.116.75) by
 FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Fri, 18 Mar 2016 03:10:43 -0700
Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by
 fmsmsx158.amr.corp.intel.com (10.18.116.75) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Fri, 18 Mar 2016 03:10:44 -0700
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.136]) by
 SHSMSX103.ccr.corp.intel.com ([169.254.4.24]) with mapi id 14.03.0248.002;
 Fri, 18 Mar 2016 18:10:41 +0800
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Ilya Maximets <i.maximets@samsung.com>, Yuanhan Liu
 <yuanhan.liu@linux.intel.com>, Thomas Monjalon <thomas.monjalon@6wind.com>
CC: "dev@dpdk.org" <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>
Thread-Topic: [dpdk-dev] [PATCH RFC v3 0/3] Thread safe
 rte_vhost_enqueue_burst().
Thread-Index: AdGA/mzh7qkKnzflTgm5RKDWe5MQGA==
Date: Fri, 18 Mar 2016 10:10:41 +0000
Message-ID: <C37D651A908B024F974696C65296B57B4C677AF2@SHSMSX101.ccr.corp.intel.com>
References: <1456314438-4021-1-git-send-email-i.maximets@samsung.com>
 <9470086.ZYvecjaNVJ@xps13> <20160318091614.GT979@yliu-dev.sh.intel.com>
 <3519170.fnd0yd7nVF@xps13> <20160318094642.GA23215@yliu-dev.sh.intel.com>
 <56EBD085.4030500@samsung.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH RFC v3 0/3] Thread safe
 rte_vhost_enqueue_burst().
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Fri, 18 Mar 2016 10:10:45 -0000

On 3/18/2016 5:55 PM, Ilya Maximets wrote:=0A=
> Hi all.=0A=
> And what about first patch of this series:=0A=
> "vhost: use SMP barriers instead of compiler ones." ?=0A=
>=0A=
> It's not about thread safety in terms of 'lockless'. It is the standalone=
=0A=
> patch that fixes many times discussed issue with barriers on arm.=0A=
>=0A=
> Best regards, Ilya Maximets.=0A=
Right, for ARM. I put a comment there. Btw, could you add -in-reply-to=0A=
when you send you next patch?=0A=