On 2/13/2018 10:06 AM, Burakov, Anatoly wrote:
> 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
>> Slot: 0000:00:05.0
>> Class: Unclassified device [00ff]
>> Vendor: Red Hat, Inc [1af4]
>> Device: Virtio memory balloon 
>> SVendor: Red Hat, Inc [1af4]
>> SDevice: Device 
>> PhySlot: 5
>> Driver: virtio-pci
>> It is a little different with the standard "Ethernet" controller, such as
>> "Class: Ethernet controller ".
>> 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?
Can we call it "memory_devices" instead of "avp_devices" ?
>> Xiaohua Zhang
>> -----Original Message-----
>> 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?