From: Kevin Wolf <kwolf@redhat.com>
To: Josef Bacik <josef@redhat.com>
Cc: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-kernel@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: BTRFS: Unbelievably slow with kvm/qemu
Date: Tue, 13 Jul 2010 10:53:48 +0200 [thread overview]
Message-ID: <4C3C299C.20306@redhat.com> (raw)
In-Reply-To: <20100712134347.GB15754@dhcp231-156.rdu.redhat.com>
Am 12.07.2010 15:43, schrieb Josef Bacik:
> On Mon, Jul 12, 2010 at 03:34:44PM +0200, Giangiacomo Mariotti wrote:
>> On Mon, Jul 12, 2010 at 9:09 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
>>>
>>> This looks quite similar to a problem with ext4 and O_SYNC which I
>>> reported earlier but no one cared to answer (or read?) - there:
>>> http://permalink.gmane.org/gmane.linux.file-systems/42758
>>> (sent to qemu-devel and linux-fsdevel lists - Cc'd too). You can
>>> try a few other options, esp. cache=none and re-writing some guest
>>> files to verify.
>>>
>>> /mjt
>>>
>> Either way, changing to cache=none I suspect wouldn't tell me much,
>> because if it's as slow as before, it's still unusable and if instead
>> it's even slower, well it'd be even more unusable, so I wouldn't be
>> able to tell the difference. What I can say for certain is that with
>> the exact same virtual hd file, same options, same system, but on an
>> ext3 fs there's no problem at all, on a Btrfs is not just slower, it
>> takes ages.
>>
>
> O_DIRECT support was just introduced recently, please try on the latest kernel
> with the normal settings (which IIRC uses O_DIRECT), that should make things
> suck alot less.
IIUC, he uses the default cache option of qemu, which is
cache=writethrough and maps to O_DSYNC without O_DIRECT. O_DIRECT would
only be used for cache=none.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Giangiacomo Mariotti <gg.mariotti@gmail.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-kernel@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: BTRFS: Unbelievably slow with kvm/qemu
Date: Tue, 13 Jul 2010 10:53:48 +0200 [thread overview]
Message-ID: <4C3C299C.20306@redhat.com> (raw)
In-Reply-To: <20100712134347.GB15754@dhcp231-156.rdu.redhat.com>
Am 12.07.2010 15:43, schrieb Josef Bacik:
> On Mon, Jul 12, 2010 at 03:34:44PM +0200, Giangiacomo Mariotti wrote:
>> On Mon, Jul 12, 2010 at 9:09 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
>>>
>>> This looks quite similar to a problem with ext4 and O_SYNC which I
>>> reported earlier but no one cared to answer (or read?) - there:
>>> http://permalink.gmane.org/gmane.linux.file-systems/42758
>>> (sent to qemu-devel and linux-fsdevel lists - Cc'd too). You can
>>> try a few other options, esp. cache=none and re-writing some guest
>>> files to verify.
>>>
>>> /mjt
>>>
>> Either way, changing to cache=none I suspect wouldn't tell me much,
>> because if it's as slow as before, it's still unusable and if instead
>> it's even slower, well it'd be even more unusable, so I wouldn't be
>> able to tell the difference. What I can say for certain is that with
>> the exact same virtual hd file, same options, same system, but on an
>> ext3 fs there's no problem at all, on a Btrfs is not just slower, it
>> takes ages.
>>
>
> O_DIRECT support was just introduced recently, please try on the latest kernel
> with the normal settings (which IIRC uses O_DIRECT), that should make things
> suck alot less.
IIUC, he uses the default cache option of qemu, which is
cache=writethrough and maps to O_DSYNC without O_DIRECT. O_DIRECT would
only be used for cache=none.
Kevin
next prev parent reply other threads:[~2010-07-13 8:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 5:24 BTRFS: Unbelievably slow with kvm/qemu Giangiacomo Mariotti
2010-07-12 5:54 ` Justin P. Mattock
2010-07-12 7:09 ` Michael Tokarev
2010-07-12 7:09 ` [Qemu-devel] " Michael Tokarev
2010-07-12 7:17 ` Justin P. Mattock
2010-07-12 7:17 ` [Qemu-devel] " Justin P. Mattock
2010-07-12 13:15 ` Giangiacomo Mariotti
2010-07-12 13:15 ` [Qemu-devel] " Giangiacomo Mariotti
2010-07-12 13:15 ` Giangiacomo Mariotti
2010-07-12 13:34 ` Giangiacomo Mariotti
2010-07-12 13:34 ` [Qemu-devel] " Giangiacomo Mariotti
2010-07-12 13:34 ` Giangiacomo Mariotti
2010-07-12 13:40 ` Michael Tokarev
2010-07-12 13:40 ` [Qemu-devel] " Michael Tokarev
2010-07-12 13:43 ` Josef Bacik
2010-07-12 13:43 ` [Qemu-devel] " Josef Bacik
2010-07-12 13:43 ` Josef Bacik
2010-07-12 13:42 ` Michael Tokarev
2010-07-12 13:42 ` [Qemu-devel] " Michael Tokarev
2010-07-12 13:49 ` Josef Bacik
2010-07-12 13:49 ` [Qemu-devel] " Josef Bacik
2010-07-12 20:23 ` Giangiacomo Mariotti
2010-07-12 20:23 ` [Qemu-devel] " Giangiacomo Mariotti
2010-07-12 20:23 ` Giangiacomo Mariotti
2010-07-12 20:24 ` Josef Bacik
2010-07-12 20:24 ` [Qemu-devel] " Josef Bacik
2010-07-13 8:53 ` Kevin Wolf [this message]
2010-07-13 8:53 ` Kevin Wolf
2010-07-13 4:29 ` Avi Kivity
2010-07-14 2:39 ` Giangiacomo Mariotti
2010-07-14 19:49 ` Christoph Hellwig
2010-07-17 5:29 ` Giangiacomo Mariotti
2010-07-17 10:28 ` Ted Ts'o
2010-07-18 7:15 ` 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=4C3C299C.20306@redhat.com \
--to=kwolf@redhat.com \
--cc=gg.mariotti@gmail.com \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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.