From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Zhang, Xiaohua" <Xiaohua.Zhang@windriver.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] usertools/dpdk-devbind.py: add support for wind river avp device
Date: Tue, 13 Feb 2018 10:06:34 +0000 [thread overview]
Message-ID: <7669d512-828b-afaf-3f44-c14da84b0ec2@intel.com> (raw)
In-Reply-To: <5620FA0292C24E4EAAAE8FBE2DB3A7A50128936DD4@ALA-MBD.corp.ad.wrs.com>
On 13-Feb-18 1:43 AM, Zhang, Xiaohua wrote:
> Hi Anatoly,
> AVP is a virtual NIC type, so you are right.
>
> When using the AVP device, you will see the following information from lspci (example).
> Slot: 0000:00:05.0
> Class: Unclassified device [00ff]
> Vendor: Red Hat, Inc [1af4]
> Device: Virtio memory balloon [1002]
> SVendor: Red Hat, Inc [1af4]
> SDevice: Device [0005]
> PhySlot: 5
> Driver: virtio-pci
>
> It is a little different with the standard "Ethernet" controller, such as "Class: Ethernet controller [0200]".
> Theoretically, the AVP is a memory based device. That's the reason, I put it as separate catalog.
>
OK, fair enough. Is there any way we can make this category
not-WindRiver AVP specific? Are there other similar devices out there
that could potentially fit into this category?
>
> BR.
> Xiaohua Zhang
>
> -----Original Message-----
<snip>
>
> Is there any particular reason why this device appears in its own category, rather than being added to one of the existing device classes?
> I'm not familiar with AVP but it looks like it's a NIC, so shouldn't it be in network_devices category?
>
> --
> Thanks,
> Anatoly
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-02-13 10:06 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 [this message]
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
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=7669d512-828b-afaf-3f44-c14da84b0ec2@intel.com \
--to=anatoly.burakov@intel.com \
--cc=Xiaohua.Zhang@windriver.com \
--cc=dev@dpdk.org \
/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).