From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 3B9D21B650 for ; Sat, 23 Dec 2017 15:28:11 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A4E5420AFF; Sat, 23 Dec 2017 09:28:08 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 23 Dec 2017 09:28:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=/prjk8rZn32z1tHnOapp9UMFoJ FQWCBHx6RHDuNM4iE=; b=PGHl3lsKaYx7DBv4cBCer/G78whG3DSL7BSCg8Ne5G Eh7oaCmspmtwJlX97Lf6oW15cPz8CkmuU9BcD2kfiKbr2pV8KvXr7RcRQk0kvF+7 q3xbjqD8JZxWU9FTfdkXr3ROlpXWkBHoJ5xRGMpo5gR8To0YihjeAN0B+wsJ7x1g Q= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/prjk8 rZn32z1tHnOapp9UMFoJFQWCBHx6RHDuNM4iE=; b=Q4/X+bs4PuDfSZwUCmo0ln 2BAahSZidardTy+9ejHzFR/YHbFfopwNVV7GMB2B1Ik86cFKRa9/CJAPWyfEkRJS HmFo5vZafeusb8ky1pmtk2bq2YEUtKs5mHRXSAQd830seaPPEEOUdvy6X26igCCq zLhqKhCD36T+1Hk+IV+mJwRjaQLmSKLmI1hwil6Dta2BAP+yH9cDKYz3nowE0xDu eY9y9fdD9v93KJCeWxIOLhJYHJYJdgIOHxkyJGTBSKrG1cE/Zx9gBQgJfSygLhsL uzJWW+vYujTfYKLNiY3BY4u6xxuYVGUtVhfaXrAAE0AwrvZUOB/PxiMOh4dSAUkw == X-ME-Sender: Received: from xps.localnet (206.83.136.77.rev.sfr.net [77.136.83.206]) by mail.messagingengine.com (Postfix) with ESMTPA id 3920124250; Sat, 23 Dec 2017 09:28:08 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, Adrien Mazarguil , Ferruh Yigit Date: Sat, 23 Dec 2017 15:28:06 +0100 Message-ID: <3029007.9n0dD63hBa@xps> In-Reply-To: References: <20171218162443.12971-1-adrien.mazarguil@6wind.com> <20171222173846.20731-1-adrien.mazarguil@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/5] Introduce virtual PMD for Hyper-V/Azure platforms 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: , X-List-Received-Date: Sat, 23 Dec 2017 14:28:11 -0000 23/12/2017 03:06, Stephen Hemminger: > Why does this need to be a PMD? It needs to be a driver on top of buses. > Maybe we need some platform infrastructure? What would be such infrastructure? A new driver type? Something like drivers/platform/? I am not sure it is required for this driver given it is most probably only a temporary driver waiting for the NetVSC PMD and a full hotplug support in DPDK internals. I think we should create such new infrastructure only when we are sure it is needed permanently for some drivers. > My definition of PMD is it can send and receive It is the definition of an ethdev driver, yes.