Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors
From: Avi Kivity <hidden>
Date: 2011-12-04 16:34:04
Also in:
kvm, lkml
Possibly related (same subject, not in this thread)
- 2011-12-09 · Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors · Rusty Russell <hidden>
- 2011-12-08 · Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors · Sasha Levin <hidden>
- 2011-12-07 · Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors · Avi Kivity <hidden>
- 2011-11-29 · Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors · "Michael S. Tsirkin" <mst@redhat.com>
- 2011-11-29 · Re: [PATCH] virtio-ring: Use threshold for switching to indirect descriptors · Sasha Levin <hidden>
On 12/04/2011 06:00 PM, Michael S. Tsirkin wrote:
quoted
If you copy descriptors, then it goes away.The avail ring could go away. used could if we make descriptors writeable. IIUC it was made RO in the hope that will make it easier for xen to adopt. Still relevant?
You mean RO from the consumer side? Why can't Xen do that?
quoted
That does suck. Are there issues in increasing the ring size? Or making it discontiguous?discontiguous ring is what indirect is, basically.
No, discontiguous is more cache and prefetch friendly. With vmap(), the code doesn't even change. -- error compiling committee.c: too many arguments to function