From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 1D30725D9;
 Wed,  8 Aug 2018 09:23:51 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 99B27202D1;
 Wed,  8 Aug 2018 03:23:50 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute1.internal (MEProxy); Wed, 08 Aug 2018 03:23:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=uzidBMbzewNcchFKzF82I4Dz12
 fWSQTFE/4Zu3Z0MQ4=; b=Y6Uhm+kCied7PMyIJYSOv0un1tQt23oS5TZJUraLSW
 vjk+MUys8aFguEyCSGQUDR9mlCqbuPuuGsrD3A1AdVRXuYnXtFU1dxcjKil94P7G
 BzECnmCg67Min5gb2qR69gvtcADc8DtZlsvilLZwtFCBE3N7jy0FrEZst+m+wI1m
 o=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=uzidBM
 bzewNcchFKzF82I4Dz12fWSQTFE/4Zu3Z0MQ4=; b=cE1amNhq99IaqaLnwfOTi5
 wPff1tQgk76gbACH2QEQ2sPJkR5PYJK+v1hIeZxEDYZymROoqFtLk8npW9zftG+Z
 mGa/yhkAbsVQGuCosc4TWql19dFOzgHqqh0JKF2p3KbYiaxIh7wneOpiMgNfFSHE
 ZWZ26OIBc3z55WmEemio43C6dxY4TF3ynRSIk0CXEa6/XFANYZ5iN3L1WMoOzee+
 BdWqiMH9SlQyBut/xK31DOFCvQYbW7AB/bF0D26emYFYca9Jmb6/ZLD255b7YKrq
 CCDwfGMXAr9IBFV3HcelTiT/phnpp769/5f3K5R5rSj/V189WPQGt2XHuNuWSIQA
 ==
X-ME-Proxy: <xmx:hZpqW-SmOG6V0OM8U606LyG-JU3rBn3YS5M7GWf_lkWHn_QaCkyvIw>
 <xmx:hZpqWz_diJpEG9U4o6fAkCEod-8rCltvV5Q33xG_PSBHHi25MZIdlw>
 <xmx:hZpqW9oW-4L5lR2Eh4zrHJr81UEtsUIyM59ClHpuezjFCnAXynvT1Q>
 <xmx:hZpqW4kUL2La45FqTFFEnS75OkoBVRgKVcQuAddFR9RbBXPvucoNpg>
 <xmx:hZpqW8K_YnTP-gf7a41EYUKh0m-bni9ybQt_5yTKZjA2dH4I-ibfQA>
 <xmx:hppqW1VI9lqq0VmIfxVKe48FJsqayaca_1WFzvLjINU0Q9c0W_OGjA>
X-ME-Sender: <xms:hZpqWw9vSvAb5v4gn-iFDebJ8TyBs8faruQaJ4PxSh2iCh7uNwmRMQ>
Received: from xps.localnet (114.149.6.93.rev.sfr.net [93.6.149.114])
 by mail.messagingengine.com (Postfix) with ESMTPA id 6B47C10268;
 Wed,  8 Aug 2018 03:23:48 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Hu <Gavin.Hu@arm.com>
Cc: stable@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>, "He,
 Jia" <jia.he@hxt-semitech.com>, "dev@dpdk.org" <dev@dpdk.org>,
 Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
 Steve Capper <Steve.Capper@arm.com>, Ola Liljedahl <Ola.Liljedahl@arm.com>,
 "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Date: Wed, 08 Aug 2018 09:23:47 +0200
Message-ID: <2000874.KblcnO9OXq@xps>
In-Reply-To: <20180808030730.GA19236@jerin>
References: <20180806011805.7857-1-gavin.hu@arm.com>
 <VI1PR08MB31679A894D5DE6C6839C49588F270@VI1PR08MB3167.eurprd08.prod.outlook.com>
 <20180808030730.GA19236@jerin>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] ring: fix c11 memory
	ordering issue
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2018 07:23:51 -0000

08/08/2018 05:07, Jerin Jacob:
> From: Gavin Hu <Gavin.Hu@arm.com>
> > 
> > Hi Jia,
> > 
> > Thanks for your feedback, let's see if there are requests from others to split the fix.
> 
> +1 to split it as small patches. If possible, 4 patches, 2 for bug fix
> and 2 for optimization.
> 
> Like you mentioned over all performance improvement data, Please add it
> per optimization patch if possible.

Yes each fix deserves a separate patch with full explanation
of the bug, how it is fixed and how much it is improved.