From: Theodore Tso <tytso@mit.edu>
To: Nick Piggin <nickpiggin@yahoo.com.au>,
Daniel Phillips <phillips@phunq.net>,
linux-fsdevel@vger.kernel.org, tux3@tux3.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available
Date: Mon, 16 Mar 2009 02:38:30 -0400 [thread overview]
Message-ID: <20090316063830.GC6357@mit.edu> (raw)
In-Reply-To: <20090316051211.GB26138@disturbed>
Dave,
It wasn't my intention to say that XFS was bad; in fact, I thought I
was actually complementing XFS by talking about some of the advanced
features that XFS had (many of which I have always said that ext3 has,
and some of which ext4 still does not have, and probably never will
have). I stand corrected on some of the details that I got wrong.
What I was trying to say was that *if* (and perhaps I'm
misunderstanding fsblock) that fsblock is requiring that as soon as a
page is dirty, fsblock requests the filesystem to assign a block
allocation to the buffers attached to the dirty page, that this would
spike out delayed allocation, which would be unfortunate for *both*
ext4 and XFS.
But maybe I'm misunderstanding what fsblock is doing, and there isn't
a problem here.
Regards,
- Ted
next prev parent reply other threads:[~2009-03-16 6:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 16:25 Tux3 report: Tux3 Git tree available Daniel Phillips
2009-03-11 18:42 ` Andrew Morton
2009-03-12 5:38 ` [Tux3] " Daniel Phillips
2009-03-12 6:07 ` Andrew Morton
2009-03-12 8:33 ` Daniel Phillips
2009-03-12 8:47 ` Nick Piggin
2009-03-12 9:00 ` Daniel Phillips
2009-03-12 9:10 ` Nick Piggin
2009-03-12 10:15 ` Daniel Phillips
2009-03-12 11:03 ` Nick Piggin
2009-03-12 12:24 ` Daniel Phillips
2009-03-12 12:32 ` Matthew Wilcox
2009-03-12 12:45 ` Nick Piggin
2009-03-12 13:12 ` Daniel Phillips
2009-03-12 13:06 ` Daniel Phillips
2009-03-12 13:04 ` Nick Piggin
2009-03-12 13:59 ` Matthew Wilcox
2009-03-12 14:19 ` Nick Piggin
2009-03-15 3:24 ` Daniel Phillips
2009-03-15 3:50 ` Nick Piggin
2009-03-15 4:08 ` Daniel Phillips
2009-03-15 4:14 ` Nick Piggin
2009-03-15 2:41 ` Daniel Phillips
2009-03-15 3:45 ` Nick Piggin
2009-03-15 21:44 ` Theodore Tso
2009-03-15 22:41 ` Daniel Phillips
2009-03-16 10:32 ` Nick Piggin
2009-03-16 5:12 ` Dave Chinner
2009-03-16 6:38 ` Theodore Tso [this message]
2009-03-16 10:14 ` Nick Piggin
2009-03-12 17:06 ` Theodore Tso
2009-03-13 9:32 ` Nick Piggin
2009-03-12 17:00 ` OGAWA Hirofumi
2009-03-15 3:54 ` Daniel Phillips
2009-03-12 9:47 ` Sam Ravnborg
2009-03-12 10:25 ` Daniel Phillips
2009-03-12 15:30 ` Diego Calleja
2009-03-12 16:54 ` OGAWA Hirofumi
2009-03-15 3:36 ` Daniel Phillips
2009-03-15 4:26 ` OGAWA Hirofumi
2009-03-12 13:24 ` Andi Kleen
2009-03-12 21:24 ` [Tux3] " Daniel Phillips
2009-03-12 23:38 ` Andi Kleen
2009-03-15 3:03 ` Daniel Phillips
2009-03-12 21:02 ` Roland Dreier
2009-03-15 4:02 ` Daniel Phillips
2009-03-12 16:18 ` OGAWA Hirofumi
2009-03-12 20:02 ` Andrew Morton
2009-03-12 20:46 ` OGAWA Hirofumi
2009-03-15 3:58 ` Daniel Phillips
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=20090316063830.GC6357@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=phillips@phunq.net \
--cc=tux3@tux3.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