From: Reinoud Zandijk <reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: How does NILFS2 handle directory management
Date: Mon, 28 Sep 2009 00:10:49 +0200 [thread overview]
Message-ID: <20090927221049.GA14618@aardappel.13thmonkey.org> (raw)
In-Reply-To: <20090926.101634.31873031.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi Ryusuke,
On Sat, Sep 26, 2009 at 10:16:34AM +0900, Ryusuke Konishi wrote:
> > The Ext3 approach also is hacky and shoe-horned. How can it even see if the
> > hash table is still OK? an Ext2 system could have radically reformed and
> > reformatted the dirents.
>
> One of the reason I see it as a candidate is that it keeps both
> backward and forward compatibility. And, we can see the applicable
> code in front of our eyes.
Ext3 hash correctness detection thus works ONLY if the first entry is indeed
recycled on a directory entry creation. If not, its pointing to garbage.....
> > I'll mail the source-snippets to you privately; but thats'll have to wait till
> > tomorrow. Please do remind me if you haven't recieved them!
>
> Well, could you share the reference to the snippet on this list? I
> think Sekiba-san also has interest in the code.
Sure! I'll first try to fixup the code a bit more since i noticed that the
free-space detection in Ext2 type direntries is euhm... hackish, just like in
FFS btw ;)
I've added a `compactable directory' bit now in the directory readin. If no
free space is found on insertion that can be reused directly (i.e. fits inside
a free space), it now knows it can issue a directory compaction. This
compaction can either compact the entire directory in one go or only compact
the broken up blocks; followed up by a rehash.
So i'll be experimenting a bit more and let you know.
With regards,
Reinoud
next prev parent reply other threads:[~2009-09-27 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 19:16 How does NILFS2 handle directory management Prasenjit Giri
[not found] ` <2324ff2b0909101216q31dad1a8y43ea0f229923a0c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-10 19:26 ` Reinoud Zandijk
[not found] ` <20090910192619.GA1263-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2009-09-11 1:21 ` Ryusuke Konishi
[not found] ` <20090911.102118.69189169.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-11 3:48 ` Jiro SEKIBA
[not found] ` <873a6u16qy.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-09-11 4:13 ` Ryusuke Konishi
2009-09-11 3:58 ` Prasenjit Giri
[not found] ` <2324ff2b0909102058g1ee407fco3f2482b4732dacca-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-11 6:23 ` Ryusuke Konishi
2009-09-11 5:22 ` Reinoud Zandijk
[not found] ` <20090911052213.GA24899-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-11 6:44 ` Ryusuke Konishi
[not found] ` <20090911.154452.43227079.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-14 10:27 ` Reinoud Zandijk
[not found] ` <20090914102731.GA154-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-24 8:49 ` Jiro SEKIBA
[not found] ` <87hbusbud6.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-09-25 12:21 ` Reinoud Zandijk
[not found] ` <20090925122109.GD6624-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-25 15:47 ` Ryusuke Konishi
[not found] ` <20090926.004730.113223425.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-25 16:23 ` Reinoud Zandijk
[not found] ` <20090925162334.GA14945-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-26 1:16 ` Ryusuke Konishi
[not found] ` <20090926.101634.31873031.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-27 22:10 ` Reinoud Zandijk [this message]
[not found] ` <20090927221049.GA14618-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-27 23:03 ` Jiro SEKIBA
2009-09-27 11:34 ` Jiro SEKIBA
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=20090927221049.GA14618@aardappel.13thmonkey.org \
--to=reinoud-s783fymb3ccdnm+yrofe0a@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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