From: Jamie Lokier <jamie@shareable.org>
To: Mark McLoughlin <markmc@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] virtio indirect ring entries
Date: Wed, 17 Jun 2009 12:44:55 +0100 [thread overview]
Message-ID: <20090617114455.GB27947@shareable.org> (raw)
In-Reply-To: <1245234943.27028.38.camel@blaa>
Mark McLoughlin wrote:
> Indirect ring entries has been merged for 2.6.31, these patches
> implement the qemu side.
I like the idea of increasing the ring capacity, but I see that this
method still has limitations, and the effective capacity depends on
the I/O submission pattern, which isn't very friendly.
Has arbitrarily expandable rings (using tail pointer ring entries)
ever been considered?
-- Jamie
next prev parent reply other threads:[~2009-06-17 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 10:35 [Qemu-devel] [PATCH 0/2] virtio indirect ring entries Mark McLoughlin
2009-06-17 10:37 ` [Qemu-devel] [PATCH 1/2] virtio: make vring_desc_*() take phys addrs Mark McLoughlin
2009-06-17 10:38 ` [Qemu-devel] [PATCH 2/2] virtio: add support for indirect ring entries Mark McLoughlin
2009-06-17 11:44 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-18 17:24 [Qemu-devel] [PATCH 0/2] virtio: " Mark McLoughlin
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=20090617114455.GB27947@shareable.org \
--to=jamie@shareable.org \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.