From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v4 3/6] bus: introduce device level DMA memory mapping Date: Wed, 13 Mar 2019 12:19:22 +0100 Message-ID: <1907286.xmCKSEcAjO@xps> References: <1698312.TEgN2QzQvo@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "anatoly.burakov@intel.com" , "dev@dpdk.org" , Yongseok Koh , "ferruh.yigit@intel.com" , "nhorman@tuxdriver.com" , "gaetan.rivet@6wind.com" To: Shahaf Shuler Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 9BB16568A for ; Wed, 13 Mar 2019 12:19:26 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 13/03/2019 12:12, Shahaf Shuler: > From: Thomas Monjalon > > > +/** > > > + * Device level DMA map function. > > > + * After a successful call, the memory segment will be mapped to the > > > + * given device. > > > + * > > > + * @note: Memory must be registered in advance using rte_extmem_* > > APIs. > > > > Could we make more explicit that this function is part of the "external > > memory API"? > > How do you suggest? There could be an explicit comment. > This function belongs to rte_dev therefore the rte_dev prefix. better rte_dev_extmem_dma_map ? Not sure about the prefix. Anatoly?