All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] raw/linux-aio: Also initialize POSIX AIO
Date: Sun, 25 Oct 2009 08:19:07 +0100	[thread overview]
Message-ID: <20091025071907.GA17121@lst.de> (raw)
In-Reply-To: <4AE02073.6030403@redhat.com>

On Thu, Oct 22, 2009 at 11:05:55AM +0200, Kevin Wolf wrote:
> Yes, it might look like overkill to introduce a abstraction for exactly
> two backends. I felt the same way. But then, the current implementation
> just feels totally wrong. It absolutely intransparent when we fall back
> to paio, and before debugging the bdrv_read/write emulation I didn't
> even know that we're doing it. And, like I said, why should a block
> format driver know what AIO method works which way?

Because the aio method is part of the block driver.  Despite our
code organization linux-aio.c and compat-posix-aio.c aren't generic
abstractions but sub-modules of raw-posix.  They would be better of
beeing renamed to block/raw-posix-aio-linux.c and
block/raw-posix-aio-pthreads.c, but with the latency of getting patches
into qemu that would just make developing any block code a nightmare
while those patches are in the queue.

  reply	other threads:[~2009-10-25  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  9:33 [Qemu-devel] [PATCH] raw/linux-aio: Also initialize POSIX AIO Kevin Wolf
2009-10-20 10:12 ` [Qemu-devel] " Kevin Wolf
2009-10-22  8:31   ` Christoph Hellwig
2009-10-22  9:05     ` Kevin Wolf
2009-10-25  7:19       ` Christoph Hellwig [this message]
2009-10-26  8:36         ` Kevin Wolf
2009-10-28  8:37           ` 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=20091025071907.GA17121@lst.de \
    --to=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 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.