From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D227AA0561; Thu, 18 Mar 2021 11:45:50 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8DC1D406B4; Thu, 18 Mar 2021 11:45:50 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id D6B4C40698; Thu, 18 Mar 2021 11:45:49 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 4BF1B5C0172; Thu, 18 Mar 2021 06:45:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 18 Mar 2021 06:45:49 -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=fm3; bh= WztwlezuPoNZ+U10Xd01pBFfZzpA/si+zOa9QK3sDmw=; b=of4PnbCSujRjnMBu rHMbk+KBbgRpQReCTDp4Fiu+xtp69dXUoT9P/Dk7aeU1GF0qb0vvaklBkGZ9oAuf b6mdclPXK1aycZaVJSjpwcbr5GzqHTG0W1g7K8Sh2MZm5Tbca14hYNYw1aPCciL6 JOsWhpOaTz2o67sIlGxklEHDA5Y1oCuFudryn7DcfkCK+LlEYfV5z8xzu/wpobXM TNLB1ShbBE8bPNJS8lNBOitTDqKXbks06gzw7rAEnq3rDnVgaoWonC9qL6GRSdvW /j021pMhEA5hHMEUOne2aVX3efCAkEqnAWqImHATHb/hsVQpkkxpE2FQz/ZPinO/ L+vx3g== 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=WztwlezuPoNZ+U10Xd01pBFfZzpA/si+zOa9QK3sD mw=; b=FN/1abXK8YCxOZJnlZZNCCYxEhwzL+LL8LP4HAbp/m90ax6ouASvhfsIv 99m0ihaf7vW4zqvhOIgwP2voaaOVc9grP067/AQhZ0H3dTx0yZGzfAeQk5BYNx9S WJ2+D7KTWGI4ssyM95eRcCIIUfb6yhjXTKin25ZlB33HE/D+NZurYf2cS9ET0d2A BRf6e3r1rktw4dfu+sCiHuydw8PeKPrznyDDUhJtsdmcWOM1X+x4nQVayqeIQGjw +csJ3aKqvNHYNh7xBy/R/3baq5TewMIKSKOy1HvT66F98dWnhzJszU2O7tz3rVJb EvkayePJkpgm8xz8Xph15ZVZRRsQw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefiedgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght 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 B04B31080063; Thu, 18 Mar 2021 06:45:47 -0400 (EDT) From: Thomas Monjalon To: Slava Ovsiienko Cc: "dev@dpdk.org" , "dmitry.kozliuk@gmail.com" , "stable@dpdk.org" , Tal Shnaiderman , Narcisa Vasile , Ranjit Menon , John Alexander , Pallavi Kadam Date: Thu, 18 Mar 2021 11:45:45 +0100 Message-ID: <1804735.jvUaWJhmuk@thomas> In-Reply-To: References: <20210316231153.724029-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] bus/pci: fix Windows kernel driver categories X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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/03/2021 09:36, Slava Ovsiienko: > From: Thomas Monjalon > > In Windows probing, the value RTE_PCI_KDRV_NONE was used instead of > > RTE_PCI_KDRV_UNKNOWN (mlx case), and RTE_PCI_KDRV_NIC_UIO > > (FreeBSD) was re-used instead of having a new RTE_PCI_KDRV_NET_UIO for > > Windows NetUIO. > > As far as I understand - under Windows there is always some kernel driver > backing the device, hence, RTE_PCI_KDRV_NONE is not an option and > RTE_PCI_KDRV_UNKNOWN is more appropriate. I would add this extra > explanation in commit message. The reason is that NONE is not appropriate because there *is* a kernel driver backing the device in mlx case. And it is aligning with Linux. I will improve the message and comments.