From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yongseok Koh Subject: Re: [PATCH v2 1/2] mbuf: add function returning default buffer address Date: Thu, 10 Jan 2019 18:22:08 +0000 Message-ID: References: <20190109085426.39965-1-yskoh@mellanox.com> <20190109131908.4949-1-yskoh@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: Olivier Matz , Shahaf Shuler , "dev@dpdk.org" To: David Marchand Return-path: Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00059.outbound.protection.outlook.com [40.107.0.59]) by dpdk.org (Postfix) with ESMTP id 8FDF11B885 for ; Thu, 10 Jan 2019 19:22:09 +0100 (CET) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Jan 9, 2019, at 5:46 AM, David Marchand > wrote: On Wed, Jan 9, 2019 at 2:19 PM Yongseok Koh > wrote: This patch introduces two new functions - rte_mbuf_buf_addr_default() and rte_mbuf_data_baddr_default(). rte_mbuf_buf_addr_default() reutrns the default buffer address of given mbuf which comes after mbuf structure and private data. The buffer address should always be the same for a given mbuf, there is no = "default" value for it, there is only one value. So for me s/rte_mbuf_buf_addr_default/rte_mbuf_buf_addr/g. +1 rte_mbuf_data_baddr_default() returns the default address of mbuf data taking the headroom into account. Or just rte_mbuf_data_addr_default() ? +1 Signed-off-by: Yongseok Koh > Those are new functions, they should go through the EXPERIMENTAL api markin= g process. If that's the rule, I'll follow anyway, although these are too obvious to b= e experimental. Thanks, Yongseok