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 C4418A04C2; Mon, 25 Nov 2019 15:30:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 889732952; Mon, 25 Nov 2019 15:30:00 +0100 (CET) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 49FED28EE for ; Mon, 25 Nov 2019 15:29:58 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 83BF25A7A; Mon, 25 Nov 2019 09:29:57 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 25 Nov 2019 09:29:57 -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=CsTZwMg0yhLm/Hk0ldBpa3o+wjF9+fsYqjU0ZgpMcKk=; b=WT6cd1J7Ecpk avY0zAoz/8zftr5BEbkt0KtSR873SGqB7uTEEpP6remaIcFl68bK6uho1X2NwPNG NhcmIZ7pMqHvTUPSrs15DfkCA8iqGZ5mUsFp0IPl45Mv0ZYayAhQBJqfM0/fjm1m XLHm3NBomiatjKx/UzCGVgPwUgx+P00= 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=CsTZwMg0yhLm/Hk0ldBpa3o+wjF9+fsYqjU0ZgpMc Kk=; b=YDvddAW7uoEu7Q0DwmvCSZCudJSqBSeTMbdHZS/CRcHrXq+yy8j32Rmly MRet8w56Qe7yfD3Q3Npp24KLmYZtWfn9CBCCXTQ72Smj9sabUEckQCTLFxtJzDCo 2Q6AF4LZQ5k0WC9Qa/OmXQQB/8hnzFN3nG+qC80O3CsvxjS88NZ5sinaKPTye6eo 6GyKe5DXGL8zsasIWSYRFQtOa0eWqmsTvXXyFmkeVfElEFyUYCYCZG2AGkEmXQcR xO0rxy/s173bSoWqr6hV6gG7+e+S3TGvusWXRnL+9OmxhNk3zSfekrKCII68+mW2 a2kaqIFehTDZRYWaOWAQEjRK1y+6w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeiuddgieeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd 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 CD5B63060060; Mon, 25 Nov 2019 09:29:53 -0500 (EST) From: Thomas Monjalon To: "Burakov, Anatoly" Cc: David Marchand , Ferruh Yigit , Ajit Khaparde , Beilei Xing , Bruce Richardson , dev , Hyong Youb Kim , Igor Russkikh , Jerin Jacob Kollanukkaran , Jingjing Wu , "Mcnamara, John" , John Daley , Kiran Kumar Kokkilagadda , "Ananyev, Konstantin" , "Kovacevic, Marko" , Matan Azrad , Nithin Dabilpuram , Pavel Belous , Qi Zhang , Qiming Yang , Rasesh Mody , Shahaf Shuler , Shahed Shaikh , Somnath Kotur , Viacheslav Ovsiienko , Wenzhuo Lu , Xiao Wang , Yongseok Koh Date: Mon, 25 Nov 2019 15:29:52 +0100 Message-ID: <2263279.lvETuDcYzU@xps> In-Reply-To: <7aeaca3a-fc13-c440-2d6f-947c24def572@intel.com> References: <1563800213-29839-3-git-send-email-david.marchand@redhat.com> <7aeaca3a-fc13-c440-2d6f-947c24def572@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 2/4] eal: fix IOVA mode selection as VA for PCI drivers 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" 25/11/2019 13:58, Burakov, Anatoly: > On 25-Nov-19 12:36 PM, David Marchand wrote: > > On Mon, Nov 25, 2019 at 1:03 PM Ferruh Yigit wrote: > >>>> I would like to get your comment on the issue. > >>>> > >>>> For the OvS mode, hopefully binding the device to 'vfio-pci' > >>>> can be a solution, but for the cases we don't have that option, > >>>> can/should we force the DPDK to PA mode after initialization? > >>> > >>> I think this is expected, because VA is the new default since 19.08: > >>> http://doc.dpdk.org/guides/rel_notes/release_19_08.html#new-features > >>> > >>> In case, there is no constraint on initialization, > >>> we have to decide which mode is preferred. > >>> Previously PA was preferred. > >>> For the sake of modernity (and because it fits with some new devices), > >>> the preference has been changed to VA. > >>> > >>> If igb_uio device is used at initialization, > >>> the PA mode should be used. > >>> If igb_uio (PA-only) device is hotplugged, no luck! > >>> If VA-only device is hotplugged, it works! > >>> > >>> I think this change is one step in deprecating igb_uio. > >>> > >> > >> I just want to confirm/clarify that this behavior change is by design, not a defect. > >> Should we document this behavior change more clearly, or highlight more, to not > >> let catch others too? > > > > The behavior change happened with: > > https://git.dpdk.org/dpdk/commit?id=bbe29a9bd7ab6feab9a52051c32092a94ee886eb > > And there is an entry in the 19.08 release notes: > > http://doc.dpdk.org/guides/rel_notes/release_19_08.html#new-features > > > > > > Should we perhaps also provide LTS release notes, i.e. "all changes > since last LTS"? I think it's unreasonable to expect people using LTS's > to trace through every release notes between LTS's. I don't think it is unreasonable. There are only 4 releases since last LTS. But I am OK for switching to 3 releases per year :)