From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gage Eads Subject: [PATCH v4] doc: announce ring API change Date: Fri, 1 Feb 2019 08:36:23 -0600 Message-ID: <20190201143623.31135-1-gage.eads@intel.com> References: <20190118153117.23810-1-gage.eads@intel.com> Cc: olivier.matz@6wind.com, arybchenko@solarflare.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, stephen@networkplumber.org, Honnappa.Nagarahalli@arm.com, gavin.hu@arm.com, Ola.Liljedahl@arm.com, nd@arm.com To: dev@dpdk.org Return-path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 6183F1B4D6 for ; Fri, 1 Feb 2019 15:35:53 +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" 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.08. [1] http://mails.dpdk.org/archives/dev/2019-January/124162.html Signed-off-by: Gage Eads --- v4: - 19.05 -> 19.08 v3: - "two changes are planned" -> "one change is planned" v2: - Drop the ABI change notice doc/guides/rel_notes/deprecation.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index d4aea4b46..93509e23a 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -83,3 +83,9 @@ Deprecation Notices - The size and layout of ``rte_cryptodev_qp_conf`` and syntax of ``rte_cryptodev_queue_pair_setup`` will change to to allow to use two different mempools for crypto and device private sessions. + +* ring: one change is planned for rte_ring in v19.08: + + - 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). -- 2.13.6