qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
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, 01 Sep 2009 20:00:58 +0300	[thread overview]
Message-ID: <4A9D534A.10105@redhat.com> (raw)
In-Reply-To: <4A9D46EA.8090606@codemonkey.ws>

On 09/01/2009 07:08 PM, Anthony Liguori wrote:
>
> I don't like the interface either although I'm not sure if the 
> alternative is better.   A different way to do this would be to have a 
> queuing API.   A device would queue requests and then kick the queue.  
> This is closer to how virtio-blk works.
>

The other end would simply collect the requests in an array and call 
multiwrite when the queue is kicked.

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

  parent reply	other threads:[~2009-09-01 17:01 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
2009-09-01 17:00     ` Avi Kivity [this message]
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=4A9D534A.10105@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=hch@lst.de \
    --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).