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 B4D6D1B44E for ; Fri, 1 Feb 2019 12:16:44 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3679921D4E; Fri, 1 Feb 2019 06:16:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 01 Feb 2019 06:16:44 -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=3miiuiIzX9VnaQ964W8FN0/X4ym6n7ql0p9I6XYpzN0=; b=nSr31TcLWGef mHGyeJXXORhq/t9vw95pGh3ruOaH24MW/ZR/mux4CFdwXGDsEf7lzsPQUaU7BBxb 8xoDTWIo8gd1mbUBtHIEEU7NyeD9B8s1WhbhI/MgjfyYnZy7rWl1a0ONlBlrr3wX s2cuKMQrSTgHddPmXOYQbJD24ha/Uxk= 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=3miiuiIzX9VnaQ964W8FN0/X4ym6n7ql0p9I6XYpz N0=; b=B0sUPa0rYPDxjVgrgAGiBHC6EwZSRzLKtI3iY8908IYw9lDqEExFW+XUJ IYQSpcR3DMfEGLmwnuk8ipvi+aWNTRF0q1dcgvEPVDosMR0wATlwXuz543YP+192 60Zm7t9bjDhI08THB38N1faI24ru9FGpKrUlEh5QD5dvEuLN7uZ5NkcmLcOSfJA1 cRQDRI66pO1jCBEQHTvPiY7LDF/OzhICLoThCJsf9c+OQnr02N8BYy8QJW2YgitT 04XU0JzVJpeM0IABAYu2MraWiwvtoLqI/2tl1XYxLMIrpxtVDTGY/c3MuNJFkkHR HvbaNuweunUSvsikb5DAzbMlk90ag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeekgddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukhdroh hrghenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivg eptd 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 0AFCFE40FF; Fri, 1 Feb 2019 06:16:41 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org, Gage Eads Cc: olivier.matz@6wind.com, arybchenko@solarflare.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, stephen@networkplumber.org, john.mcnamara@intel.com Date: Fri, 01 Feb 2019 12:16:41 +0100 Message-ID: <172114315.O9AQeyJeYo@xps> In-Reply-To: <20190118153117.23810-1-gage.eads@intel.com> References: <20190118152844.23297-1-gage.eads@intel.com> <20190118153117.23810-1-gage.eads@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] doc: announce ring API change 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: Fri, 01 Feb 2019 11:16:44 -0000 18/01/2019 16:31, Gage Eads: > In order to support the non-blocking ring[1], an API change (additional > argument to rte_ring_get_memsize()) is required in librte_ring. This commit > updates the deprecation notice to pave the way for its inclusion in > 19.05. > > [1] http://mails.dpdk.org/archives/dev/2019-January/123774.html > > Signed-off-by: Gage Eads Nobody agreed on this change. Gage, do you still want to push non-blocking ring in 19.05? --- > +* ring: one change is planned for rte_ring in v19.05: > + > + - rte_ring_get_memsize() will get a new ``flags`` parameter, so it can > + calculate the memory required for rings that require more than 8B per entry > + (such as the upcoming non-blocking ring).