From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B5F81A04C2; Tue, 26 Nov 2019 00:32:43 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 267DA2952; Tue, 26 Nov 2019 00:32:42 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id E4E1D235 for ; Tue, 26 Nov 2019 00:32:40 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 859BF226E0; Mon, 25 Nov 2019 18:32:40 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 25 Nov 2019 18:32:40 -0500 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=pUKK1RjgN6nLSleu9YyNBPwzwRQ0ykMiz+aBrPZLWDg=; b=VXQjGbDhtV4/ 34obKhPob4AbHYndc+nCzOpT9pPH9oNpjo+C7TxeF9wl/v3ZLUHFixQCiEjXRsuZ 8QTw1rRtQE8gV8snshNqOSA10buJkPI9gRqdcbXQ6xnFU+wSJWQZKnLJka7IZVTX PCmwRWSeoDloY6UyRRRW03PikA50GZU= 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=fm1; bh=pUKK1RjgN6nLSleu9YyNBPwzwRQ0ykMiz+aBrPZLW Dg=; b=qGBBWGYn6gxTQilF+JA15as+BGU+5EI17n0YimFq9jrErcT9MhHhDWGZu HG1GxVM9xHY5BN9ZOEUP5V3u/wO3/UtMg38V/9aZxkP2qLSq5dFR1CwilIohsweV nOeaOC6GUaWLHnKQOR5dbL2wohVUBfzcSIOdGGZ15S6qvSDg3/WmUyTLnfKXSWwM i0SOOdd5AZwdcDLvI4Xi0/xgrIv/SqRjt8HLUXLyx4iSt62yrhFVqPLlM9UaYPjz 9JCh3TJ2lHd4lgxs3dmqYmCau42fBU3nyMw/lj0oAR2r38MwwLlHLrSGryEEcdpF 8KsGN8VPEhYD07DK/Huo8lDo34zvw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeivddgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 81155306005B; Mon, 25 Nov 2019 18:32:39 -0500 (EST) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, Olivier Matz Date: Tue, 26 Nov 2019 00:32:38 +0100 Message-ID: <6968599.34HkkUUQbD@xps> In-Reply-To: <20191118131421.GD8680@platinum> References: <9ac0f4b480cec8cbe8a9910a68f9d564641c2f41.1573740779.git.anatoly.burakov@intel.com> <20191118131421.GD8680@platinum> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] mem: clarify documentation for rte_mem_virt2iova 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 18/11/2019 14:14, Olivier Matz: > On Thu, Nov 14, 2019 at 02:13:06PM +0000, Anatoly Burakov wrote: > > It may not be immediately clear that rte_mem_virt2iova does not actually > > check the internal memseg table, and will instead either return VA (in > > IOVA as VA mode), or will fall back to kernel page table walk (in IOVA > > as PA mode). > > > > Add a note to API documentation indicating the above. > > > > Signed-off-by: Anatoly Burakov > > Reviewed-by: Olivier Matz Applied, thanks