From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v4 3/6] bus: introduce device level DMA
	memory mapping
Date: Sat, 30 Mar 2019 15:36:49 +0100
Message-ID: <3303376.pHsfKVRZFs@xps>
References: <cover.1551793527.git.shahafs@mellanox.com>
 <1698312.TEgN2QzQvo@xps>
 <AM0PR0502MB3795D92D8DB68B66A5823F28C34A0@AM0PR0502MB3795.eurprd05.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, "anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
 Yongseok Koh <yskoh@mellanox.com>,
 "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
 "nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
 "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 9A437493D
 for <dev@dpdk.org>; Sat, 30 Mar 2019 15:36:54 +0100 (CET)
In-Reply-To: <AM0PR0502MB3795D92D8DB68B66A5823F28C34A0@AM0PR0502MB3795.eurprd05.prod.outlook.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

13/03/2019 12:12, Shahaf Shuler:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 10/03/2019 09:28, Shahaf Shuler:
> > > For PCI bus devices, the pci driver can expose its own map and unmap
> > > functions to be used for the mapping. In case the driver doesn't
> > > provide any, the memory will be mapped, if possible, to IOMMU through
> > VFIO APIs.
> > >
> > > Application usage with those APIs is quite simple:
> > > * allocate memory
> > > * call rte_extmem_register on the memory chunk.
> > > * take a device, and query its rte_device.
> > > * call the device specific mapping function for this device.
> > 
> > Should we make it documented somewhere?
> 
> The full flow to work w/ external memory is documented at doc/guides/prog_guide/env_abstraction_layer.rst , Subchapter "Support for Externally Allocated Memory.
> The last commit in series update the right API to use.

OK, then I will move this doc update in this patch.