From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 1/2] Add bdrv_aio_multiwrite
Date: Fri, 11 Sep 2009 00:44:01 +0200 [thread overview]
Message-ID: <20090910224401.GB25700@lst.de> (raw)
In-Reply-To: <1252511618-19497-2-git-send-email-kwolf@redhat.com>
One thing that concerns me here is that we keep adding more memory
allocations to the I/O path. At least on fast SSDs even kernel memory
allocations are a performance problem and they're much faster than
userspace ones.
next prev parent reply other threads:[~2009-09-10 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:53 [Qemu-devel] [PATCH v3 0/2] block: Handle multiple write requests at once Kevin Wolf
2009-09-09 15:53 ` [Qemu-devel] [PATCH v3 1/2] Add bdrv_aio_multiwrite Kevin Wolf
[not found] ` <m3ocpj67ip.fsf@neno.mitica>
2009-09-10 7:07 ` [Qemu-devel] " Kevin Wolf
2009-09-10 22:44 ` Christoph Hellwig [this message]
2009-09-11 6:29 ` [Qemu-devel] " Kevin Wolf
2009-09-11 18:36 ` Christoph Hellwig
2009-09-09 15:53 ` [Qemu-devel] [PATCH v3 2/2] virtio-blk: Use bdrv_aio_multiwrite Kevin Wolf
2009-09-10 22:41 ` Christoph Hellwig
2009-09-11 7:10 ` Kevin Wolf
2009-09-11 18:39 ` 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=20090910224401.GB25700@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 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).