Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Konstantin Khlebnikov <khlebnikov@parallels.com>,
	"penberg@kernel.org" <penberg@kernel.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"asias.hejun@gmail.com" <asias.hejun@gmail.com>,
	"gorcunov@gmail.com" <gorcunov@gmail.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] kvm tools: Add scatter-gather variants of IO functions
Date: Sun, 17 Apr 2011 15:49:45 +0300	[thread overview]
Message-ID: <4DAAE1E9.8000502@redhat.com> (raw)
In-Reply-To: <1303038717.3017.18.camel@stimpy>

On 04/17/2011 02:11 PM, Sasha Levin wrote:
> I don't think it's worth delaying the next readv() to run through
> read_in_full, and whats more, the part we're going to read again is
> probably sitting in the file cache anyway.

If you have a file cache.  High performance often means bypassing the 
cache, and in those cases submitting guest requests exactly as the guest 
passed them is important.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-04-17 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 15:05 [PATCH 1/2 V2] kvm tools: Add scatter-gather variants of IO functions Sasha Levin
2011-04-16 15:05 ` [PATCH 2/2 V2] kvm tools: Add scatter-gather support for disk images Sasha Levin
2011-04-16 18:40 ` [PATCH 1/2 V2] kvm tools: Add scatter-gather variants of IO functions Konstantin Khlebnikov
2011-04-16 20:33   ` Sasha Levin
2011-04-17  9:19   ` Avi Kivity
2011-04-17 10:03     ` Konstantin Khlebnikov
2011-04-17 10:22       ` Sasha Levin
2011-04-17 10:34         ` Konstantin Khlebnikov
2011-04-17 11:11           ` Sasha Levin
2011-04-17 12:49             ` Avi Kivity [this message]

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=4DAAE1E9.8000502@redhat.com \
    --to=avi@redhat.com \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=khlebnikov@parallels.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox