From: Josef Bacik <josef@redhat.com>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-kernel@vger.kernel.org, Josef Bacik <josef@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: BTRFS: Unbelievably slow with kvm/qemu
Date: Mon, 12 Jul 2010 16:24:25 -0400 [thread overview]
Message-ID: <20100712202424.GC2881@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimWPLqEf4LjHx39zO7yzkJ_c157OjOm3UnBRgJ2@mail.gmail.com>
On Mon, Jul 12, 2010 at 10:23:14PM +0200, Giangiacomo Mariotti wrote:
> On Mon, Jul 12, 2010 at 3:43 PM, Josef Bacik <josef@redhat.com> 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,
> >
> > Josef
> >
> With latest kernel do you mean the current Linus' git tree? Because if
> instead you're talking about the current stable kernel, that's the one
> I used on my test.
>
Yes Linus' git tree. Thanks,
Josef
next prev parent reply other threads:[~2010-07-12 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin1uF6WbVvxJ84oO1NKnCU-6VHrmWU1XFYTlqtp@mail.gmail.com>
2010-07-12 7:09 ` [Qemu-devel] Re: BTRFS: Unbelievably slow with kvm/qemu 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
2010-07-12 13:49 ` Josef Bacik
2010-07-12 20:23 ` Giangiacomo Mariotti
2010-07-12 20:24 ` Josef Bacik [this message]
2010-07-13 8:53 ` Kevin Wolf
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=20100712202424.GC2881@localhost.localdomain \
--to=josef@redhat.com \
--cc=gg.mariotti@gmail.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 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).