From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3] doc: announce ring API change Date: Fri, 01 Feb 2019 12:16:41 +0100 Message-ID: <172114315.O9AQeyJeYo@xps> References: <20190118152844.23297-1-gage.eads@intel.com> <20190118153117.23810-1-gage.eads@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: olivier.matz@6wind.com, arybchenko@solarflare.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, stephen@networkplumber.org, john.mcnamara@intel.com To: dev@dpdk.org, Gage Eads 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) In-Reply-To: <20190118153117.23810-1-gage.eads@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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).