From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v1 0/3] Introduce virtual PMD for Hyper-V/Azure platforms Date: Mon, 18 Dec 2017 16:40:01 -0800 Message-ID: References: <20171124172132.GW4062@6wind.com> <20171218162443.12971-1-adrien.mazarguil@6wind.com> <20171218102304.66b2e98d@xeon-e3> <8750482.grKP3id3vm@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: dev@dpdk.org, Adrien Mazarguil , Ferruh Yigit To: Thomas Monjalon Return-path: Received: from mail-pl0-f65.google.com (mail-pl0-f65.google.com [209.85.160.65]) by dpdk.org (Postfix) with ESMTP id 728BA271 for ; Tue, 19 Dec 2017 01:40:03 +0100 (CET) Received: by mail-pl0-f65.google.com with SMTP id n13so5895167plp.11 for ; Mon, 18 Dec 2017 16:40:03 -0800 (PST) In-Reply-To: <8750482.grKP3id3vm@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Dec 18, 2017 at 12:13 PM, Thomas Monjalon wrote: > 18/12/2017 19:23, Stephen Hemminger: > > Please don't call this drivers/net/hyperv/ > > that name conflicts with the real netvsc PMD that I am working on. > > > > Maybe vdev-netvsc? > > I expect your PMD to be in drivers/net/netvsc/ > Why is it conflicting with drivers/net/hyperv/ ? > > > > The naming is a bit confusing, and I am willing to change it since not upstream. The code uses mostly BSD driver which doesn't call itself netvsc. Instead the BSD driver uses hn_ as a prefix for most visible data and functions. Have been trying to name netvsc to avoid confusion with the kernel driver. Like any name it is completely irrelevant to functionality.