From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 1195CA05D3 for ; Sat, 30 Mar 2019 01:23:12 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C1A983256; Sat, 30 Mar 2019 01:23:10 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 830642BD3 for ; Sat, 30 Mar 2019 01:23:09 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 15BAF21C5C; Fri, 29 Mar 2019 20:23:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 20:23:09 -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=x/4KCpML5h5+NvfgR4djFIYrpP/KH17Jf6+H2hRHObg=; b=rLXwJf75i9rt jFIIahnuoeh9Dfi+lDaKc8FBM1DGmvVbFeFYlX4oRycl1T34oGewf76w6lWLbAQf BAUxUc+KxjDLfdW8g0bLfMUf2nZUzxLBt2CxAL2LUJQnjj30f6ZJTcriYllyZXkt Xu+/A+QQKzbKtrciJ23YrQYGwTi3ApQ= 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=x/4KCpML5h5+NvfgR4djFIYrpP/KH17Jf6+H2hRHO bg=; b=Kny2ijzu6Tia37P2vgRPLEY8ozaNcy2fC566IBAQrt1GBFUoCb6Cr5Kpw 2RRxbByNHcHz0dxJvyvgT7CFn7TuKYLoLfG1x6auIy/FpNaLx/SHm3e+XGNFdn12 jh82ZPTOizV68N44xNRaoitrbETgeYk2ibDgQRw3xMDd8ueiYrVp4GxAcTonnh4U sMv5J19jhusAQD2AQXraMnUr+0QRJbDZFpAtkFw8Ok89NS6UFC4ZHmL9Jqst5WUh a4hlLmHjVzMFQlbMBtgVNBhsUacZxV1CZ/FFswOP5Mx6KDE4wZsajeM7PRzq+MGG 5AGMTMYsGe7lCIDB2u4I7pgg59Mxw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeekgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 13E29E46C1; Fri, 29 Mar 2019 20:23:06 -0400 (EDT) From: Thomas Monjalon To: Shahaf Shuler Cc: dev@dpdk.org, anatoly.burakov@intel.com, yskoh@mellanox.com, ferruh.yigit@intel.com, nhorman@tuxdriver.com, gaetan.rivet@6wind.com Date: Sat, 30 Mar 2019 01:23:05 +0100 Message-ID: <1932739.UiCEsj7Gze@xps> In-Reply-To: <828c4b2a57c5f6c4753898a6d3e96f0f9ded8171.1552206210.git.shahafs@mellanox.com> References: <828c4b2a57c5f6c4753898a6d3e96f0f9ded8171.1552206210.git.shahafs@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v4 1/6] vfio: allow DMA map of memory for the default vfio fd 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" Message-ID: <20190330002305.YrOwWmQcRZy9-BUFaRP95mQn4DnbMXeoN3IzSqdJSec@z> 10/03/2019 09:27, Shahaf Shuler: > Enable users the option to call rte_vfio_dma_map with request to map > to the default vfio fd. > > Signed-off-by: Shahaf Shuler > Acked-by: Anatoly Burakov > --- > --- a/doc/guides/rel_notes/release_19_05.rst > +++ b/doc/guides/rel_notes/release_19_05.rst > @@ -136,6 +136,9 @@ ABI Changes > +* vfio: Functions ``rte_vfio_container_dma_map`` and > + ``rte_vfio_container_dma_unmap`` have been extended with an option to > + request mapping or un-mapping to the default vfio container fd. Isn't it an API change rather than ABI? It is adding -1 as a special value, I think it is not breaking previous interface, and does not require a notification in the release notes.