From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 75D451B1EA for ; Wed, 2 Jan 2019 13:51:01 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B02FC21E5A; Wed, 2 Jan 2019 07:50:59 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 02 Jan 2019 07:50:59 -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=QCYnBtyUm9ON0uSmHdGLRvDj8mZapBY3cYMrlcG0e6E=; b=qgsBxl6MnasO iJC3oLwb7wmNDeFjM1nPTyvQjdDbZ40CWMEQFSCRDnyA+jI10pexIKiVawEhJsV4 EaCCVSBm4DM88cNmoBlwK4WXzyhGVN+fabaD0v4qIlgMjPFR46RjiCujC5Ofsjr9 Q6muD1cmWW3knjE++TMVKS0pfPwq/JY= 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=fm1; bh=QCYnBtyUm9ON0uSmHdGLRvDj8mZapBY3cYMrlcG0e 6E=; b=LJa7cZiFayjfVDeUHZF0z0jrD4pJ3PqheNvDeNOhH7NKjLU3BpgzDiBFY 0eaTqC3On5txNw6AQTEiHFpEPdkGv9mNSVW8AyCHBocdSmSl5tsD6QIyeuvBYmCT sgSxd8ZNClh0RkdJMYczL/koA3N6D4tAyfwnKB9155Ku81qXBTxIiO/nO2YpqaEW kfEoL48N87ReeK180k6X/bsyo05wdOH9RpmbMeaWmGIU+TGb6ZKkIjD4OHBitYBS g4PwIbFL9pOulq7jdDyizYAFlbygwoUGrvZJ2HYI5syQ3wcVEIbjI5z0JiKQ6TLU 8xkRWm7smASR0GXZBtbQxq3OMgrGw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrudeigdegfeculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu 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 B88F710106; Wed, 2 Jan 2019 07:50:57 -0500 (EST) From: Thomas Monjalon To: Gavin Hu Cc: dev@dpdk.org, jerinj@marvell.com, hemant.agrawal@nxp.com, bruce.richardson@intel.com, chaozhu@linux.vnet.ibm.com, Honnappa.Nagarahalli@arm.com, nd@arm.com, olivier.matz@6wind.com Date: Wed, 02 Jan 2019 13:50:55 +0100 Message-ID: <3304696.9C1FQTdO3e@xps> In-Reply-To: <1546390533-53868-1-git-send-email-gavin.hu@arm.com> References: <1546390533-53868-1-git-send-email-gavin.hu@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 0/3] add rte ring reset api and use it to flush a ring by hash 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: , X-List-Received-Date: Wed, 02 Jan 2019 12:51:01 -0000 02/01/2019 01:55, Gavin Hu: > V4: Include the ring perf test case enhancement patch in the series. > > V3: Allow experimental API for meson build > > V2: Fix the coding style issue(commit message line too long) > > V1: To flush a ring not in use, dequeue one by one is wasting cpu cycles. > The patch is to just resetting the head and tail indices to save cpu > cycle. It is too late for adding this API in 19.02, but we should review and give opinion, so it will be ready to integrate in early February.