qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>, Christoph Hellwig <hch@lst.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] block: Handle multiple write requests at once
Date: Tue, 1 Sep 2009 18:14:57 +0200	[thread overview]
Message-ID: <20090901161457.GA23349@lst.de> (raw)
In-Reply-To: <4A9D46EA.8090606@codemonkey.ws>

On Tue, Sep 01, 2009 at 11:08:10AM -0500, Anthony Liguori wrote:
> Or introduce a helper layer that coalesces requests that lives outside 
> of the core block API.

I'm not even sure we need much of a helper.  It's just a slightly
smarter way to build the qiov - instead of submitting the qiov once
we're done with one request poke into the next one and add it to
if it fits, else submit the request.  Also submit it if no more
request is pending.

  reply	other threads:[~2009-09-01 16:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 13:51 [Qemu-devel] [PATCH 0/3] block: Handle multiple write requests at once Kevin Wolf
2009-09-01 13:51 ` [Qemu-devel] [PATCH 1/3] Add bdrv_aio_multiwrite Kevin Wolf
2009-09-01 13:51 ` [Qemu-devel] [PATCH 2/3] virtio-blk: Use bdrv_aio_multiwrite Kevin Wolf
2009-09-01 13:51 ` [Qemu-devel] [PATCH 3/3] qcow2: Add bdrv_aio_multiwrite implementation Kevin Wolf
2009-09-01 15:52 ` [Qemu-devel] [PATCH 0/3] block: Handle multiple write requests at once Christoph Hellwig
2009-09-01 16:08   ` Anthony Liguori
2009-09-01 16:14     ` Christoph Hellwig [this message]
2009-09-01 17:00     ` Avi Kivity
2009-09-01 16:59   ` Avi Kivity
2009-09-02  7:27   ` Kevin Wolf
2009-09-02 15:43     ` Christoph Hellwig
2009-09-02 15:50       ` Kevin Wolf
2009-09-02 17:26         ` Christoph Hellwig

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=20090901161457.GA23349@lst.de \
    --to=hch@lst.de \
    --cc=anthony@codemonkey.ws \
    --cc=kwolf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).