From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 757B51B223 for ; Mon, 6 Nov 2017 09:37:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D0F9220BC2; Mon, 6 Nov 2017 03:37:29 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 06 Nov 2017 03:37:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=gbQX/3Hz9GywviRZfM+tqvS5xx Ujd7S/CwTTzHlrOkM=; b=W44OpA2nmRIUqDO1BLOICpBSD+4S0S+H3dddfqm5R2 bM36ZsNLwgZnpUsW0boYnJiWYT2XWu4u1+XIOjpugHl6clkrHO5WS4P7dZMGFMKf eR3CJxMuZvmyI9IihcBrI3cm4V49/r0U0TTV8kkZktzzTLDeD+MJxHaolNPwN1CQ I= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=gbQX/3 Hz9GywviRZfM+tqvS5xxUjd7S/CwTTzHlrOkM=; b=lYqK6l9+wyq6qEP02XphdQ S8ViFjbKJ/XyFVxSwNNDQuSPOnDOGhuq/8VWmIGh6q43l5UH+lqQxvvmfQQYDZAO fhEE8XCuJeXbUYodTIsg/j4vkhxZ8STmTAc/OGSo6qy3KIlOgiQEjtCVbs/mW/jJ r8XJxH7mMGtku4c1w7pOLF1ND84eADVYVJh7o84wwpGvCg+36cMhgFjaKHVctkLC LJvN3Vq8gbzxeizouBZplTTcqDmYwOmX/vn7hgEkpKRuVHWoVeSgNX9tSHe8164o rDKZauuSDnlsTbWRpokcrPFa9PQHB+bbaDDl/uUpw08ZxhtKQG/jl5+zy7BnzvfQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8E29D246D5; Mon, 6 Nov 2017 03:37:29 -0500 (EST) From: Thomas Monjalon To: santosh Cc: olivier.matz@6wind.com, sergio.gonzalez.monroy@intel.com, anatoly.burakov@intel.com, dev@dpdk.org Date: Mon, 06 Nov 2017 09:37:27 +0100 Message-ID: <3304743.b7VfCBXbgQ@xps> In-Reply-To: <80cb9e8f-c493-4b5f-909f-9ae233ba6541@caviumnetworks.com> References: <20170814151537.29454-1-santosh.shukla@caviumnetworks.com> <20171106014141.13266-3-thomas@monjalon.net> <80cb9e8f-c493-4b5f-909f-9ae233ba6541@caviumnetworks.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 02/15] mem: introduce IOVA type 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: Mon, 06 Nov 2017 08:37:30 -0000 06/11/2017 06:38, santosh: > > On Monday 06 November 2017 07:11 AM, Thomas Monjalon wrote: > > The IO virtual addresses may be used instead of physical addresses. > > As IOVA is more generic, it should be used in most places instead > > of physical address wording. > > > > Signed-off-by: Thomas Monjalon > > --- > > +/** > > + * IO virtual address type. > > + * When the physical addressing mode is in use, > > + * the translation from a virtual address to a physical address > > + * is a direct mapping, i.e. the same value. > > + */ > > I guess - that description applicable for iova=va mode > and for iova=pa mode - Need to do explicit virt2phy translation. > I believe you mis-wrote - s/physical addressing mode/virtual addressing mode. Not sure to understand your comment. Let me reword the description to be less ambiguous: * When the physical addressing mode (IOVA as PA) is in use, * the translation from an IO virtual address (IOVA) to a physical address * is a direct mapping, i.e. the same value. * Otherwise, in virtual mode (IOVA as VA), an IOMMU may do the translation. Is this description correct?