From: "Zhang, Xiaohua" <Xiaohua.Zhang@windriver.com>
To: "RICHARDSON, BRUCE" <bruce.richardson@intel.com>,
"BURAKOV, ANATOLY" <anatoly.burakov@intel.com>
Cc: "YIGIT, FERRUH" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] usertools/dpdk-devbind.py: add support for wind river avp device
Date: Wed, 14 Feb 2018 23:17:18 +0000 [thread overview]
Message-ID: <5620FA0292C24E4EAAAE8FBE2DB3A7A5012893DAF6@ALA-MBD.corp.ad.wrs.com> (raw)
In-Reply-To: <20180214103225.GA4512@bricha3-MOBL3.ger.corp.intel.com>
That's no problem for me to move it to the "network" catalog.
Should I generate a new patch?
BR.
Xiaohua Zhang
-----Original Message-----
From: Bruce Richardson [mailto:bruce.richardson@intel.com]
Sent: Wednesday, February 14, 2018 6:32 PM
To: BURAKOV, ANATOLY
Cc: Zhang, Xiaohua; YIGIT, FERRUH; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] usertools/dpdk-devbind.py: add support for wind river avp device
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
next prev parent reply other threads:[~2018-02-14 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 9:52 Xiaohua Zhang
2018-02-12 10:13 ` Burakov, Anatoly
2018-02-13 1:43 ` Zhang, Xiaohua
2018-02-13 10:06 ` Burakov, Anatoly
2018-02-13 11:06 ` Ferruh Yigit
2018-02-14 0:48 ` Zhang, Xiaohua
2018-02-14 9:57 ` Burakov, Anatoly
2018-02-14 10:32 ` Bruce Richardson
2018-02-14 23:17 ` Zhang, Xiaohua [this message]
2018-02-15 9:28 ` Burakov, Anatoly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5620FA0292C24E4EAAAE8FBE2DB3A7A5012893DAF6@ALA-MBD.corp.ad.wrs.com \
--to=xiaohua.zhang@windriver.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).