From: Theodore Tso <tytso@mit.edu>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Btrfs v0.16 released
Date: Sat, 16 Aug 2008 15:27:50 -0400 [thread overview]
Message-ID: <20080816192749.GA8774@mit.edu> (raw)
In-Reply-To: <1218910210.19495.25.camel@think.oraclecorp.com>
On Sat, Aug 16, 2008 at 02:10:10PM -0400, Chris Mason wrote:
>
> I tried just the writeback_index patch and got only 4 fragmented files
> on ext4 after a compilebench run. Then I tried again and got 1200.
> Seems there is something timing dependent in here ;)
>
Yeah, the patch Aneesh sent to change where we added the inode to the
dirty list was false lead. The right fix is in the ext4 patch queue
now. I think we have the problem licked and a quick test showed it
increased the compilebench MB/s by a very tiny amount (enough so that
I wasnt sure whether or not it was measurement error), but it does
avoid the needly fragmentation.
- Ted
next prev parent reply other threads:[~2008-08-16 19:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:01 Btrfs v0.16 released Chris Mason
2008-08-07 9:08 ` Peter Zijlstra
2008-08-07 10:34 ` Chris Mason
2008-08-07 14:58 ` Chris Friesen
2008-08-07 15:07 ` tvrtko.ursulin
2008-08-07 9:14 ` Peter Zijlstra
2008-08-07 10:39 ` Chris Mason
[not found] ` <3da3b5b40808070703x4cf49471q6acc00351ba019d7@mail.gmail.com>
2008-08-07 14:06 ` Chris Mason
2008-08-07 18:02 ` Andi Kleen
2008-08-08 18:48 ` Chris Mason
2008-08-08 21:56 ` Andi Kleen
2008-08-09 1:19 ` Theodore Tso
2008-08-09 1:23 ` Andi Kleen
2008-08-09 1:23 ` Andi Kleen
2008-08-09 1:43 ` Theodore Tso
2008-08-09 1:23 ` Andi Kleen
2008-08-14 21:00 ` Chris Mason
2008-08-14 21:17 ` Andi Kleen
2008-08-15 1:25 ` Chris Mason
2008-08-15 1:39 ` Andi Kleen
2008-08-15 13:00 ` Chris Mason
2008-08-16 19:26 ` Szabolcs Szakacsits
2008-08-18 13:52 ` Chris Mason
2008-08-18 17:37 ` Szabolcs Szakacsits
2008-08-14 23:44 ` Theodore Tso
2008-08-15 1:10 ` Chris Mason
2008-08-15 12:46 ` Chris Mason
2008-08-15 13:45 ` Theodore Tso
2008-08-15 17:52 ` Chris Mason
2008-08-15 19:59 ` Theodore Tso
2008-08-15 20:37 ` Chris Mason
2008-08-16 18:10 ` Chris Mason
2008-08-16 19:27 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 19:33 btrfs-devel
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=20080816192749.GA8774@mit.edu \
--to=tytso@mit.edu \
--cc=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.