From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 321102F7D for ; Wed, 14 Feb 2018 11:32:30 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2018 02:32:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,511,1511856000"; d="scan'208";a="201046950" Received: from bricha3-mobl3.ger.corp.intel.com ([10.252.19.81]) by orsmga005.jf.intel.com with SMTP; 14 Feb 2018 02:32:27 -0800 Received: by (sSMTP sendmail emulation); Wed, 14 Feb 2018 10:32:26 +0000 Date: Wed, 14 Feb 2018 10:32:26 +0000 From: Bruce Richardson To: "Burakov, Anatoly" Cc: "Zhang, Xiaohua" , "Yigit, Ferruh" , "dev@dpdk.org" Message-ID: <20180214103225.GA4512@bricha3-MOBL3.ger.corp.intel.com> References: <1518342737-9244-1-git-send-email-xiaohua.zhang@windriver.com> <3bc80bbb-155a-c9f7-1b9d-b6e26ca42e37@intel.com> <5620FA0292C24E4EAAAE8FBE2DB3A7A50128936DD4@ALA-MBD.corp.ad.wrs.com> <7669d512-828b-afaf-3f44-c14da84b0ec2@intel.com> <5620FA0292C24E4EAAAE8FBE2DB3A7A5012893ACD3@ALA-MBD.corp.ad.wrs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.1 (2017-09-22) Subject: Re: [dpdk-dev] [PATCH] usertools/dpdk-devbind.py: add support for wind river avp device 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: Wed, 14 Feb 2018 10:32:31 -0000 On Wed, Feb 14, 2018 at 09:57:25AM +0000, Burakov, Anatoly wrote: > On 14-Feb-18 12:48 AM, Zhang, Xiaohua wrote: > > Hi Yigit and Anantoly, > > I checked the nics-17.11.pdf, the following is description: > > "The Accelerated Virtual Port (AVP) device is a shared memory based device only available > > on virtualization platforms from Wind River Systems. The Wind River Systems virtualization > > platform currently uses QEMU/KVM as its hypervisor and as such provides support for all of > > the QEMU supported virtual and/or emulated devices (e.g., virtio, e1000, etc.). The platform > > offers the virtio device type as the default device when launching a virtual machine or creating > > a virtual machine port. The AVP device is a specialized device available to customers that > > require increased throughput and decreased latency to meet the demands of their performance > > focused applications." > > > > I am afraid just "memory_device" will have some misunderstanding. > > Could we put it as "avp device (shared memory based)"? > > > > > > Hi, > > Well, from AVP PMD documentation, it seems that AVP is classified as a NIC. > Can't we just add it to the list of NICs, even if it's not Ethernet class > 0x20xx? Pattern-matching in devbind should work either way. For example, you > can see there's "cavium_pkx" already classified as a NIC, even though its > class is 08xx, not 02xx. So why not this one? > Definite +1. It's used for packet IO into a vm, like virtio, and it's driver is in drivers/net. "If it looks like a NIC, and quacks like a NIC, then it probably is a NIC". [Alternatively if it looks and quacks like a duck, I'm not sure what it's doing in DPDK!] /Bruce