On Thu, 16 Mar 2000, Hans Reiser wrote:
> Alexander Viro wrote:
> >
> > On Wed, 15 Mar 2000, Hans Reiser wrote:
> >
> > > Not sure I understand your question, but I'll take a stab at it. Currently the
> > > first directory a file is created in stays its packing locality parent for the
> > > life of the file. The packing locality parent is the first key component. So,
> > > currently, if you know the parent directory id the file was created in you know
> > > the first component of the key, and the last component of the key is the offset
> > > which you can also know. This leaves the middle of the key unknown.
> >
> > Ouch. What happens if you
> > mkdir foo
> > create foo/bar
> > rename foo/bar baz/bar
> > rmdir foo
>
> packing locality is foo.
Even though inode of foo is gone? OK, fine with me. Do you mean that your
"locality" is roughly an equivalent of cylinder group on FFS?
> I believe your other questions were answered in other emails, not all by me.
> Correct me if I err in this.
Umm... I'd still like to hear a description of your internal locking. In
particular, what do you lock/release upon reiserfs_find_entry()/pathrelse()?
When do you rebalance the tree? How do you do serialization between that
and things a-la write_inode()/readdir()/lookup()? Currently locking is
masked by the VFS one and that's one of the reasons why I want to see
cleaned variant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:23 EST