From: Michael Tokarev <mjt@tls.msk.ru>
To: Josef Bacik <josef@redhat.com>
Cc: Giangiacomo Mariotti <gg.mariotti@gmail.com>,
linux-kernel@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: BTRFS: Unbelievably slow with kvm/qemu
Date: Mon, 12 Jul 2010 17:42:04 +0400 [thread overview]
Message-ID: <4C3B1BAC.1050907@msgid.tls.msk.ru> (raw)
In-Reply-To: <20100712134347.GB15754@dhcp231-156.rdu.redhat.com>
Josef Bacik wrote:
[]
> 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. Thanks,
Um. Do you mean it were introduced in BTRFS or general? :)
Because, wel, O_DIRECT is here and supported since some 2.2 times... ;)
/mjt
next prev parent reply other threads:[~2010-07-12 13:42 UTC|newest]
Thread overview: 27+ 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:17 ` Justin P. Mattock
2010-07-12 13:15 ` Giangiacomo Mariotti
2010-07-12 13:34 ` Giangiacomo Mariotti
2010-07-12 13:40 ` Michael Tokarev
2010-07-12 13:43 ` Josef Bacik
2010-07-12 13:42 ` Michael Tokarev [this message]
2010-07-12 13:49 ` Josef Bacik
2010-07-12 20:23 ` Giangiacomo Mariotti
2010-07-12 20:24 ` Josef Bacik
2010-07-13 8:53 ` [Qemu-devel] " 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
-- strict thread matches above, loose matches on Subject: below --
2010-08-29 19:34 Tomasz Chmielewski
2010-08-30 0:14 ` Josef Bacik
2010-08-30 15:59 ` K. Richard Pixley
2010-08-31 21:46 ` Mike Fedyk
2010-08-31 22:01 ` K. Richard Pixley
[not found] ` <4C7D7B14.9020008@noir.com>
2010-09-02 0:18 ` Ted Ts'o
2010-09-02 16:36 ` K. Richard Pixley
2010-09-02 16:49 ` K. Richard Pixley
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=4C3B1BAC.1050907@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=gg.mariotti@gmail.com \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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