From: Joel Becker <jlbec@evilplan.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Proposed design for big allocation blocks for ext4
Date: Fri, 25 Feb 2011 16:03:04 -0800 [thread overview]
Message-ID: <20110226000304.GC28214@noexit> (raw)
In-Reply-To: <20110225234002.GA2924@thunk.org>
On Fri, Feb 25, 2011 at 06:40:02PM -0500, Ted Ts'o wrote:
> On Fri, Feb 25, 2011 at 01:59:25PM -0800, Joel Becker wrote:
> >
> > Why not call it a 'cluster' like the rest of us do? The term
> > 'blocksize' is overloaded enough already.
>
> Yes, good point. Allocation cluster makes a lot more sense as a name.
Thank you ;-)
> We're going to keep track of what blocks are uninitialized or not on a
> 4k basis. So that part of the ext4 code doesn't change.
Ok, good. We don't have that info, so we enjoy a lot of fun
with the various pagesize/blocksize/clustersize combinations.
> We could add complexity to do suballocations for directories, but KISS
> seems to be a much better idea for now.
Oh dear God no.
Joel
--
"Nobody loves me,
Nobody seems to care.
Troubles and worries, people,
You know I've had my share."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-02-26 0:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 2:56 Proposed design for big allocation blocks for ext4 Theodore Ts'o
2011-02-25 8:21 ` Andreas Dilger
2011-02-25 9:15 ` Rogier Wolff
2011-02-25 10:01 ` Andreas Dilger
2011-02-25 10:39 ` Rogier Wolff
2011-02-25 12:57 ` Theodore Tso
2011-02-25 18:05 ` Amir Goldstein
2011-02-25 19:04 ` Ted Ts'o
2011-02-25 19:39 ` Andreas Dilger
2011-02-25 21:24 ` Amir Goldstein
2011-02-25 21:59 ` Joel Becker
2011-02-25 23:40 ` Ted Ts'o
2011-02-26 0:03 ` Joel Becker [this message]
2011-02-26 0:31 ` Ted Ts'o
2011-02-26 0:33 ` Joel Becker
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=20110226000304.GC28214@noexit \
--to=jlbec@evilplan.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.