From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1E63EA0551; Sun, 16 Feb 2020 18:36:22 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 56E821C1D6; Sun, 16 Feb 2020 18:36:21 +0100 (CET) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by dpdk.org (Postfix) with ESMTP id D15661C1D4; Sun, 16 Feb 2020 18:36:19 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 0CD333BDF; Sun, 16 Feb 2020 12:36:19 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 16 Feb 2020 12:36:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=a8u+415S2ZdazCVqsSKjJNS1/LM5uYA8ctjisCQP0nM=; b=dD0HlcgDhEIr A8lAY7PDcXf8afE6ahvsdb4RRJ7ef9TUZR7q9bWTERPabJHnyE9AoWxBAatvT8JS u6LlvuvxLXFPZOIwBKko48x9vahtFgqM4IyoHyRMLLA2cXE7tC5KDP6muFg7bbtx s7b+ofX+geeMlQmDqzddRMGugxHW+K0= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=a8u+415S2ZdazCVqsSKjJNS1/LM5uYA8ctjisCQP0 nM=; b=kmkIVrT/I+4a8LYfaEkJpNCLJE1RvI6iFG/avHPA7U+ZO4Okr3Rn4CMVX ya4n4RKV2zi6uuD1Gi/PH8xJLO9HRNrnX+XQz1sYPJVPVAuRjJ513UxvhFtHyn6j xbAnsJYtmJp3PGMorJOAaExOHj4oNjqTY6rwhDGE/tD/YUlzSuS55zwYHbV2E/sx KB7SPDc71gU9xacr4YjYIhtMIpEeLg8opFpMI8x3TDn69LzlZAmF3veS+rIpSLGh nKMbY+b55QpA7DrOa/Ed10mObmnj8sgfnnwj2sPLWRJ/qsJw4VhcVUTLUdO9Mw9+ llrq7jCHmbRL+BJl6jlRs/mY8yQQA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrjeeggddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DAE283060BE4; Sun, 16 Feb 2020 12:36:16 -0500 (EST) From: Thomas Monjalon To: Ye Xiaolong Cc: ferruh.yigit@intel.com, Gavin Hu , dev@dpdk.org, nd@arm.com, david.marchand@redhat.com, jerinj@marvell.com, Honnappa.Nagarahalli@arm.com, ruifeng.wang@arm.com, phil.yang@arm.com, joyce.kong@arm.com, steve.capper@arm.com, stable@dpdk.org Date: Sun, 16 Feb 2020 18:36:15 +0100 Message-ID: <7358516.3yuU7cT3dn@xps> In-Reply-To: <20200216163849.GA60672@intel.com> References: <1571758074-16445-1-git-send-email-gavin.hu@arm.com> <1739253.u6TykanW85@xps> <20200216163849.GA60672@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4] net/i40e: relaxed barrier in the tx fastpath X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 16/02/2020 17:38, Ye Xiaolong: > Hi, Thomas > > On 02/16, Thomas Monjalon wrote: > >15/02/2020 16:16, Ye Xiaolong: > >> s/relaxed/relax > >> > >> On 02/12, Gavin Hu wrote: > >> >To keep ordering of mixed accesses, rte_cio is sufficient. > >> >The rte_io barrier inside the I40E_PCI_REG_WRITE is overkill.[1] > >[...] > >> > >> Applied to dpdk-next-net-intel with Jerin's Reviewed-by tag, Thanks. > > > >I assume it is too much risky doing such optimization post-rc3. > > Yes, this iss a valid concern, I agree to postpone it to next release. > > > > >Ferruh, Xiaolong, you don't plan anymore pull from dpdk-next-net-intel > >in 20.02? > > There are still some bug fixing work going on in PRC, so I assume there > should be some fix patches after RC3, they are still allowed to be merged > to 20.02, if the fix is relatively small in terms of lines of code and scope, > right? Right