From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id AF3C7A05D3
	for <public@inbox.dpdk.org>; Sat, 30 Mar 2019 15:36:56 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id C95E24C91;
	Sat, 30 Mar 2019 15:36:55 +0100 (CET)
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)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 15E01217D0;
 Sat, 30 Mar 2019 10:36:54 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute1.internal (MEProxy); Sat, 30 Mar 2019 10:36:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding:content-type; s=mesmtp;
 bh=7wsRTJgQz/ER2TFAQokVdQ5ExQlAITfG5o8Z+VfbywY=; b=h9PkgNdD5OL7
 VmeO/VlNr6wYjM75zO3QQtDfpg0AbB+hW1HaY9enifJBzoChQT5mdfK+CqFAxd/D
 E8tFwx9aipnamtXSnkyQbO9pjuq4nsRLEDNOnbJMQ0VcaiQcjnz3ZcQHN6aHYqih
 6kVXRsLsn7qCR23Cz3FYd/kYAG73rn4=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm2; bh=7wsRTJgQz/ER2TFAQokVdQ5ExQlAITfG5o8Z+Vfby
 wY=; b=1M3uBwPtBD4dM82sMo6xLLEg/PgJ8Xt+d+F+ONQfLWZdGJXyz+Pt6TLgP
 tofXKXkkR6fmpyRL+Y53eEq8lN/bEZa0rtnjJTfHHqu6cQyPTyVhsyk7md+b7T6p
 jEbK5o0tZTuebooRk8qzv1M9ZAg4w8F3GTxZ9I3oDN2FQ04gf5wYwZ7pk2hy7MdV
 G0eidmzedsRAjfOQkGsuLdNnYK9/g+ZbIXQor1EJAf9nMoAsdNceuqOLFsw1161z
 vEHH8/0dHvJn1/flo/DmHjBUpwvSqzshFD+kfvb6gbCO2MTW24v2y141N7PuaZ/+
 kjjOGT4x82HHqTJdGVvn4j5dJUocg==
X-ME-Sender: <xms:BH-fXFnYaYRJ_QAvuPK5vcMikH2feTZ_XV6sez87gkCIGvYLscHoEA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeelgdeikecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
 fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs
 ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph
 epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho
 mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:BH-fXFEJorpll1WTfq0kJDYkgTYxKJABak3h1Z8nl53IWjjpPIJZlw>
 <xmx:BH-fXGqqs6H0AKR8Oko4mDW6eIRm6MMDDHWwNo6HAsFHgYF6UjcqZA>
 <xmx:BH-fXJ7UUVmofOSTupoB4GrHavqU0vLOvlLZJSLT2Dpe7q6jH5_w_g>
 <xmx:Bn-fXI_Mh82WnrFES5qQQKn6FEfvuuhWmDx82zzLxbfVrwv_xldgbg>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id ED6A1E498E;
 Sat, 30 Mar 2019 10:36:50 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>
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>
Date: Sat, 30 Mar 2019 15:36:49 +0100
Message-ID: <3303376.pHsfKVRZFs@xps>
In-Reply-To: <AM0PR0502MB3795D92D8DB68B66A5823F28C34A0@AM0PR0502MB3795.eurprd05.prod.outlook.com>
References: <cover.1551793527.git.shahafs@mellanox.com>
 <1698312.TEgN2QzQvo@xps>
 <AM0PR0502MB3795D92D8DB68B66A5823F28C34A0@AM0PR0502MB3795.eurprd05.prod.outlook.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [dpdk-dev] [PATCH v4 3/6] bus: introduce device level DMA
	memory mapping
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
Message-ID: <20190330143649.IW7oBVAywY5kpPoGXeu1eYYzCMHXY46BjynX__n2FFY@z>

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.