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 15586A046B for ; Mon, 22 Jul 2019 17:55:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7FFA81BEB3; Mon, 22 Jul 2019 17:55:18 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id A252D1BEB2 for ; Mon, 22 Jul 2019 17:55:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3B35A22223; Mon, 22 Jul 2019 11:55:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 22 Jul 2019 11:55:13 -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=AS/buAnRQgPTf0oHKu1+2EK8Ztz2tWTOTnd2dvkC7ZU=; b=ZNW1pk0eUcXW r5wZs9VCjfjiIkzxR+cqMyw+pzetHmm2SScfksrwAfupmlipn2BMuLAxn441U7rG AvdAjvoyLrhsZBh0cU6mXPONrxiTJ38nI9JyxyTjcDU+tcpLcDLq/cEr8uiIyGKC cy8aAE1jDVuvTlElS4pPVRWWyOBT5RA= 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=fm3; bh=AS/buAnRQgPTf0oHKu1+2EK8Ztz2tWTOTnd2dvkC7 ZU=; b=Eg/ST6oU0IG1teKbYNuKP6Ql31zE2C/zzlUVQ9MSLHefzg/+DrGJFrAR3 TEPSSKyxq1ozBt7KtsMh0YDBnvUvqaxePTCJHRurH16wiCu96CCnM4yBozgHy81o hHuzLSdHo4ONVE0jCjpGXikPRGxPH2+vZD47LYSrdwFL9x60c6wH4clVSDqK7xB4 Dlyj5utdQAE1bGl9gvAIFPph/zEO3gvv1KBJsiujeO3mQTfVyAO48VigzUhY6BDn ozYPbz1zPRI53GN4MwXr4ObfgwKCmx7iUXc7UtiFLSMy+uGsruZ5h4cNATmkYGCR OFrfuNl/WTYvXWrSiiB1Y6x6bUq5w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrjeeggdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucfr rghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenuc evlhhushhtvghrufhiiigvpedt 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 E4F2D80064; Mon, 22 Jul 2019 11:55:11 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, Stephen Hemminger Date: Mon, 22 Jul 2019 17:55:09 +0200 Message-ID: <2082970.WY5cZRJGLO@xps> In-Reply-To: <1951993.R3ThFuq71D@xps> References: <20190607230841.17125-1-stephen@networkplumber.org> <20190709073907.5efa21e2@hermes.lan> <1951993.R3ThFuq71D@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] Revert "net/mlx: support IOVA VA mode" 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" 11/07/2019 00:18, Thomas Monjalon: > 09/07/2019 16:39, Stephen Hemminger: > > On Fri, 7 Jun 2019 16:08:41 -0700 > > Stephen Hemminger wrote: > > > > > From: Stephen Hemminger > > > > > > This reverts commit 69c06d0e357ed0064b498d510d169603cf7308cd. > > > That commit breaks support for netvsc PMD with MLX SRIOV > > > on both Hyper-V and Azure. > > > > > > Signed-off-by: Stephen Hemminger > > > > DPDK 19.08-rc is broken on Azure. This patch which seems to have been > > ignored fixes it. > > This patch was not ignored. I was waiting for the IOVA changes > to settle down. As a result, the revert will happen because the > type RTE_KDRV_NIC_MLX is not needed anymore: > https://patches.dpdk.org/patch/56314/ The revert is applied on master now. > However, I don't understand how it is related to netvsc PMD. > Please could you give more details? Please did you investigate what happened?