From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 0/5] Introduce virtual PMD for Hyper-V/Azure platforms Date: Sat, 23 Dec 2017 15:28:06 +0100 Message-ID: <3029007.9n0dD63hBa@xps> References: <20171218162443.12971-1-adrien.mazarguil@6wind.com> <20171222173846.20731-1-adrien.mazarguil@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Adrien Mazarguil , Ferruh Yigit To: Stephen Hemminger 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) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.