From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] block: Handle multiple write requests at once
Date: Wed, 2 Sep 2009 19:26:06 +0200 [thread overview]
Message-ID: <20090902172606.GA28156@lst.de> (raw)
In-Reply-To: <4A9E9457.9090904@redhat.com>
On Wed, Sep 02, 2009 at 05:50:47PM +0200, Kevin Wolf wrote:
> It's a RHEL 5.3 installation, and the kernel doesn't seem to even
> provide this file. However, I think I read that this is an issue of
> relatively new kernels, so probably not?
Indeed.
> What could matter, though, is that the installer uses LVM for the
> standard layout which I'm using. Does this make a difference in that
> respect?
It should not matter. Then again it should not issue these I/O patterns
at all, but it does. Something is clearly wrong in those I/O patterns,
but given that the exist out there in the field it seems like we'll have
to deal with it. I'll look over the patch a bit more carefully to see
if there is any obviously better way to handle it.
prev parent reply other threads:[~2009-09-02 17:26 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
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 [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=20090902172606.GA28156@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.