All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com,
	gorcunov@gmail.com, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] kvm tools: Support virtio indirect buffers
Date: Mon, 28 Nov 2011 23:05:21 +0200	[thread overview]
Message-ID: <1322514321.3629.12.camel@lappy> (raw)
In-Reply-To: <1322511443.3629.7.camel@lappy>

On Mon, 2011-11-28 at 22:17 +0200, Sasha Levin wrote:
> On Mon, 2011-11-28 at 20:49 +0200, Pekka Enberg wrote:
> > On Mon, Nov 28, 2011 at 7:54 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > > Indirect buffers are ring descriptors which point to more (even more)
> > > descriptors.
> > >
> > > This can be used to increase the effective ring capacity, which helps the
> > > guest to batch large requests - very useful for blk devices.
> > >
> > > This patch also enables indirect buffers for virtio-net and virtio-blk.
> > >
> > > The patch is based on the lguest's code which does the same.
> > >
> > > Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> > 
> > In what exact way is it useful? Improved throughput? Will this have
> > negative impact on virtio block or virtio net latency?
> 
> The total size of requests is limited by the size of the virtio ring.
> This makes it hard to squeeze large requests (like the ones you usually
> see with blk devices) into the ring. This patch simply makes each entry
> in the virtio ring point to another descriptor list, thus it allows to
> squeeze much more requests into a singe virtio ring.
> 
> It shouldn't hurt latency.
> 
> I tried getting benchmarks with it, but the results I get from fio are
> all over the place and I can't seem to get a steady result (bad sign for
> my poor spindle disk).

btw, on an unrelated subject, I think that with this patch we've fully
covered the virtio spec, and as far as I know it's the first userspace
implementation which covers the entire spec :)

-- 

Sasha.


  reply	other threads:[~2011-11-28 21:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 17:54 [PATCH] kvm tools: Support virtio indirect buffers Sasha Levin
2011-11-28 18:49 ` Pekka Enberg
2011-11-28 20:17   ` Sasha Levin
2011-11-28 21:05     ` Sasha Levin [this message]
2011-11-30  5:20       ` Rusty Russell
2011-11-29  6:31 ` Cyrill Gorcunov
2011-11-29  7:45   ` Sasha Levin
2011-11-29 13:01     ` Pekka Enberg
2011-11-29 13:06       ` Cyrill Gorcunov

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=1322514321.3629.12.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.