From: Johann Lombardi <johann.lombardi@bull.net>
To: Daniel Phillips <phillips@google.com>,
Andreas Dilger <adilger@clusterfs.com>,
sho@tnes.nec.co.jp
Cc: cmm@us.ibm.com, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/2] ext3: enlarge blocksize and fix rec_len overflow
Date: Fri, 30 Jun 2006 11:31:14 +0200 [thread overview]
Message-ID: <20060630093113.GA2702@chiva> (raw)
In-Reply-To: <44A450BB.60105@google.com>
Hi,
> >I have no objection to this at all, but I think it will lead to a slightly
> >more complex implementation. We even discussed in the distant past to
> >make large directories a series of 4kB "chunks", for fs blocksize >= 4kB.
> >This has negative implications for large filenames because the internal
> >free space fragmentation is high, but has the advantage that it might
> >eventually still be usable if we can get blocksize > PAGE_SIZE.
> >
> >The difficulty is that when freeing dir entires you would have to be
> >concerned with a merging a dir_entry that is spanning the middle
> >of a 2^16 block.
>
> That is easy, just don't let an entry span subblocks by not letting
> delete merge past the end of a subblock, just a minor tweak. New block
> initialization needs an outer loop on subblocks and that's it, I think.
I've been working on a patch implementing this feature. It currently works w/o
htree.
With dir_index, the difficulty is that an entry can span subblocks after a leaf
block split.
Cheers,
Johann
next prev parent reply other threads:[~2006-06-30 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 11:52 [RFC 1/2] ext3: enlarge blocksize and fix rec_len overflow sho
2006-06-28 15:50 ` Johann Lombardi
2006-06-28 20:24 ` Andreas Dilger
2006-06-29 10:46 ` [Ext2-devel] [RFC 1/2] ext3: enlarge blocksize and fix rec_lenoverflow Takashi Sato
2006-06-29 16:30 ` Andreas Dilger
2006-06-29 18:10 ` [RFC 1/2] ext3: enlarge blocksize and fix rec_len overflow Daniel Phillips
2006-06-29 20:27 ` Andreas Dilger
2006-06-29 22:14 ` Daniel Phillips
2006-06-30 9:31 ` Johann Lombardi [this message]
2006-06-30 18:19 ` Daniel Phillips
2006-07-01 8:39 ` Andreas Dilger
2006-07-01 10:27 ` Michael Tokarev
2006-07-05 18:41 ` 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=20060630093113.GA2702@chiva \
--to=johann.lombardi@bull.net \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@google.com \
--cc=sho@tnes.nec.co.jp \
/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