On Wed, 2005-07-06 at 15:51 -0400, Hubert Chan wrote: > On Wed, 06 Jul 2005 12:52:23 -0600, Jonathan Briggs <[email protected]> said: [snip] > > It still has the performance and locking problem of having to update > > every child file when moving a directory tree to a new parent. On the > > other hand, maybe the benefit is worth the cost. > > Every node should store the inode number(s) for its parent(s). Not the > path name. So you don't need to do any updates, since when you move a > tree, inode numbers don't change. You do need the updates if you change what inode is the parent. /a/b/c, /a/b/d, /a/b/e, /b mv /a/b /b Now you have to change the stored grand-parent inodes for /a/b/c, /a/b/d and /a/b/e so that they reference /b/b instead of /a/b. -- Jonathan Briggs <[email protected]> eSoft, Inc.
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: reiser4 plugins
- From: David Masover <[email protected]>
- Re: reiser4 plugins
- From: Hubert Chan <[email protected]>
- Re: reiser4 plugins
- References:
- Re: reiser4 plugins
- From: Hans Reiser <[email protected]>
- Re: reiser4 plugins
- From: "Alexander G. M. Smith" <[email protected]>
- Re: reiser4 plugins
- From: Hubert Chan <[email protected]>
- Re: reiser4 plugins
- From: Hans Reiser <[email protected]>
- Re: reiser4 plugins
- From: Jonathan Briggs <[email protected]>
- Re: reiser4 plugins
- From: Hubert Chan <[email protected]>
- Re: reiser4 plugins
- Prev by Date: Re: [PATCH 2/3 (updated)] openfirmware: add sysfs nodes for open firmware devices
- Next by Date: Re: reiser4 plugins
- Previous by thread: Re: reiser4 plugins
- Next by thread: Re: reiser4 plugins
- Index(es):
