On Tue, May 09, 2000 at 10:43:57AM +0200, Trond Myklebust wrote:
> >>>>> " " == Roman V Shaposhnick <email@example.com> writes:
> > Hm, I don't know about knfsd people but I am thinking about
> > something like
> > fh_to_dentry and dentry_to_fh pair. The main idea ( suggested
> > by Al ) is to allow dentry tree to grow in two different
> > directions: from root to leaves and from leaves to root. The
> > main trick will be to select right splicer and to allow quick
> > grow for upside direction. It seems, that this will satisfy NFS
> > as is, and will provide a way for unique "external"
> > representation of the dentry tree.
> Don't forget that for the case of NFS at least, you have to be able to
> locate a file anywhere in the dentry tree from scratch after a server
> reboot (All hail the god of stateless models). An fh_to_dentry() model
> would need to do this too in an as efficient manner as possible.
Yes, of course, the whole idea is to let filesystem to decide whether it
could provide something as a rock solid invariant ( that will even survive
after reboot ) or not. And if it can, let it do this via a generic interface.
Thus the filesystem will be consider exportable if it has non trivial
fh_to_dentry and dentry_to_fh -- no more wild guessing.
> I believe Neil has been working on a proposal for this within the
> knfsd project, so I've Cced him in case he was unaware of this thread.
It would be great to hear from him what is the current state of this
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:13 EST