From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from proxy.6wind.com (host.76.145.23.62.rev.coltfrance.com [62.23.145.76]) by dpdk.org (Postfix) with ESMTP id C37E9567E for ; Sun, 6 Aug 2017 23:22:40 +0200 (CEST) Received: from core.dev.6wind.com (unknown [10.0.0.1]) by proxy.6wind.com (Postfix) with ESMTPS id 558A1B076B; Sun, 6 Aug 2017 23:20:30 +0200 (CEST) Received: from [10.16.0.195] (helo=6wind.com) by core.dev.6wind.com with smtp (Exim 4.84_2) (envelope-from ) id 1deT0K-0002gD-2X; Sun, 06 Aug 2017 23:22:33 +0200 Received: by 6wind.com (sSMTP sendmail emulation); Sun, 06 Aug 2017 23:22:32 +0200 Date: Sun, 6 Aug 2017 23:22:32 +0200 From: Olivier MATZ To: Hemant Agrawal Cc: santosh , Jerin Jacob , dev@dpdk.org, thomas@monjalon.net, stephen@networkplumber.org, bruce.richardson@intel.com, shreyansh.jain@nxp.com, gaetan.rivet@6wind.com, sergio.gonzalez.monroy@intel.com, anatoly.burakov@intel.com Message-ID: <20170806212231.ar5l4qt5bxwku2mu@glumotte.dev.6wind.com> References: <20170711100141.3950-1-jerin.jacob@caviumnetworks.com> <2e51e54f-a405-3e5a-7a20-d8e97f75b5ad@caviumnetworks.com> <532ed585-cf2a-aeaf-c7e5-cca29a33925c@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <532ed585-cf2a-aeaf-c7e5-cca29a33925c@nxp.com> User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [dpdk-dev] [PATCH] eal: add notice to make DPDK IOVA aware 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: Sun, 06 Aug 2017 21:22:41 -0000 On Fri, Aug 04, 2017 at 10:55:25AM +0530, Hemant Agrawal wrote: > On 8/4/2017 9:11 AM, santosh wrote: > > On Tuesday 11 July 2017 03:31 PM, Jerin Jacob wrote: > > > > > When we run DPDK on guest or VFIO mode on host, > > > the dpdk library or device will not be directly accessing > > > the physical address. Instead, the device does go through > > > an IO address translation memory management unit. On x86, > > > we call it as IOMMU and on ARM as SMMU. > > > > > > More details: > > > http://osidays.com/osidays/wp-content/uploads/2014/12/Final_OSI2014_IOMMU_DetailedView_Sanil_Anurup.pdf > > > > > > Based on discussion in the following thread > > > http://dpdk.org/ml/archives/dev/2017-July/070850.html > > > > > > We would like to change reference to physical address to more > > > appropriate name as with IOMMU/SMMU with > > > the device won't be dealing directly with the physical address. > > > > > > An ABI change is planned for 17.11 to change following > > > data structure or functions to more appropriate name. > > > Currently planned to change it iova as instead of phys > > > > > > Please note: The change will be only for the name and > > > functional aspects of the API will remain same. > > > > > > Following functions/data structures name may change. > > > This list is based on v17.05-rc1. It may change based on v17.11 code base. > > > > > > > > > typedef: > > > phys_addr_t > > > > > > structures: > > > > > > struct rte_memseg::phys_addr > > > struct rte_mbuf::buf_physaddr > > > > > > functions: > > > rte_mempool_populate_phys() > > > rte_mempool_populate_phys_tab() > > > rte_eal_using_phys_addrs() > > > rte_mem_virt2phy() > > > rte_dump_physmem_layout() > > > rte_eal_get_physmem_layout() > > > rte_eal_get_physmem_size() > > > rte_malloc_virt2phy() > > > rte_mem_phy2mch() > > > > > > > > > Signed-off-by: Jerin Jacob > > > --- > > > > Acked-by: Santosh Shukla > > > > > Acked-by: Hemant Agrawal > Acked-by: Olivier Matz