Re: vbus design points: shm and shm-signals

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anthony Liguori wrote:
IOW, I can envision a model that looked like PCI -> virtio-pci -> virtio-shm -> virtio-ring -> virtio-net

Let me stress that what's important here is that devices target either virtio-ring or virtio-shm. If we had another transport, those drivers would be agnostic toward it. We really want to preserve the ability to use all devices over a PCI transport. That's a critical requirement for us.

The problem with vbus as it stands today, is that it presents vbus -> virtio-ring -> virtio-net and allows drivers to target either virtio-ring or vbus directly. If a driver targets vbus directly, then the driver is no longer transport agnostic and we could not support that driver over PCI.

Regards,

Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux