From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mellanox.co.il (mail-il-dmz.mellanox.com [193.47.165.129]) by dpdk.org (Postfix) with ESMTP id 9E6321B45C for ; Mon, 14 Jan 2019 06:21:05 +0100 (CET) Received: from Internal Mail-Server by MTLPINE1 (envelope-from yskoh@mellanox.com) with ESMTPS (AES256-SHA encrypted); 14 Jan 2019 07:21:01 +0200 Received: from scfae-sc-2.mti.labs.mlnx (scfae-sc-2.mti.labs.mlnx [10.101.0.96]) by labmailer.mlnx (8.13.8/8.13.8) with ESMTP id x0E5Kv82006882; Mon, 14 Jan 2019 07:21:00 +0200 From: Yongseok Koh To: konstantin.ananyev@intel.com, olivier.matz@6wind.com, thomas@monjalon.net Cc: dev@dpdk.org Date: Sun, 13 Jan 2019 21:20:55 -0800 Message-Id: <20190114052055.12896-2-yskoh@mellanox.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20190114052055.12896-1-yskoh@mellanox.com> References: <20190114052055.12896-1-yskoh@mellanox.com> Subject: [dpdk-dev] [PATCH 2/2] mbuf: remove experimental tag of external buffer attachment 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: Mon, 14 Jan 2019 05:21:06 -0000 Remove the experimental tag of rte_pktmbuf_attach_extbuf() which was introduced in 18.05. Signed-off-by: Yongseok Koh --- lib/librte_mbuf/rte_mbuf.h | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h index 6f1f7e3d8e..39df7e0a9b 100644 --- a/lib/librte_mbuf/rte_mbuf.h +++ b/lib/librte_mbuf/rte_mbuf.h @@ -1489,13 +1489,6 @@ rte_pktmbuf_ext_shinfo_init_helper(void *buf_addr, uint16_t *buf_len, * attached with appropriate free callback and its IO address. * - Smaller metadata is required to maintain shared data such as refcnt. * - * @warning - * @b EXPERIMENTAL: This API may change without prior notice. - * Once external buffer is enabled by allowing experimental API, - * ``RTE_MBUF_DIRECT()`` and ``RTE_MBUF_INDIRECT()`` are no longer - * exclusive. A mbuf can be considered direct if it is neither indirect nor - * having external buffer. - * * @param m * The pointer to the mbuf. * @param buf_addr @@ -1507,7 +1500,7 @@ rte_pktmbuf_ext_shinfo_init_helper(void *buf_addr, uint16_t *buf_len, * @param shinfo * User-provided memory for shared data of the external buffer. */ -static inline void __rte_experimental +static inline void rte_pktmbuf_attach_extbuf(struct rte_mbuf *m, void *buf_addr, rte_iova_t buf_iova, uint16_t buf_len, struct rte_mbuf_ext_shared_info *shinfo) -- 2.11.0