search for: virtio_f_window

...recommend looking at the PDF for some clarifying pictures) > > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to > guest communication. It uses a new queue extension feature tentatively > called VIRTIO_F_WINDOW which indicates that descriptor tables, > available and used rings and Queue Data reside in physical memory > ranges called Windows, each identified with an unique identifier > called WindowID. So if I had to summarize the difference from regular virtio, I'd say the main one is that t...

...recommend looking at the PDF for some clarifying pictures) > > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to > guest communication. It uses a new queue extension feature tentatively > called VIRTIO_F_WINDOW which indicates that descriptor tables, > available and used rings and Queue Data reside in physical memory > ranges called Windows, each identified with an unique identifier > called WindowID. So if I had to summarize the difference from regular virtio, I'd say the main one is that t...

...s is not necessary. IIUC the driver does not need to send all the stats. We can simply treat those stats as specific to Linux driver and other drivers will not send them. Then QEMU will treat them as if zero was reported. > > That is, the device by default supports > VIRTIO_F_LINUX, > VIRTIO_F_WINDOWS, > VIRTIO_F_BSD. > > For the Linux driver, only VIRTIO_F_LINUX is supported, then we can > have Linux specific driver implementations under that feature. Since there were no suggestions for similar stats on other OSes I'd say we treat the stats for buffers and caches as Linux sp...

...s is not necessary. IIUC the driver does not need to send all the stats. We can simply treat those stats as specific to Linux driver and other drivers will not send them. Then QEMU will treat them as if zero was reported. > > That is, the device by default supports > VIRTIO_F_LINUX, > VIRTIO_F_WINDOWS, > VIRTIO_F_BSD. > > For the Linux driver, only VIRTIO_F_LINUX is supported, then we can > have Linux specific driver implementations under that feature. Since there were no suggestions for similar stats on other OSes I'd say we treat the stats for buffers and caches as Linux sp...

On 18/09/2015 18:29, Claudio Fontana wrote: > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical memory ranges called > Windows, each identified with an unique identifier called WindowID. > Should we consider virtio-peer a pair-wise created device for two guests, where sending side...

...at the PDF for some clarifying pictures) >> >> The Virtio Peer shared memory communication device (virtio-peer) is a >> virtual device which allows high performance low latency guest to >> guest communication. It uses a new queue extension feature tentatively >> called VIRTIO_F_WINDOW which indicates that descriptor tables, >> available and used rings and Queue Data reside in physical memory >> ranges called Windows, each identified with an unique identifier >> called WindowID. > > So if I had to summarize the difference from regular virtio, > I'd...

On 18/09/2015 18:29, Claudio Fontana wrote: > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical memory ranges called > Windows, each identified with an unique identifier called WindowID. > Should we consider virtio-peer a pair-wise created device for two guests, where sending side...

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

...er) General Overview (I recommend looking at the PDF for some clarifying pictures) The Virtio Peer shared memory communication device (virtio-peer) is a virtual device which allows high performance low latency guest to guest communication. It uses a new queue extension feature tentatively called VIRTIO_F_WINDOW which indicates that descriptor tables, available and used rings and Queue Data reside in physical memory ranges called Windows, each identified with an unique identifier called WindowID. Each queue is configured to belong to a specific WindowID, and during queue identification and configuration,...