Re: [enfs-devel] More thoughts on dtree

[Lee W. <le...@sa...>]

Tramm Hudson wrote:
> 
> I wrote:
> > Scott lifted the dtree code from Linux's procfs for the most part, but
> > it is all embedded in the skelfs module.
> 
> And as I read through it, I see that it has implemented its own VFS
> internally.  That's not really efficient...

Hmm. Lifted? I hope not straight? You mean "inspired by" I hope, since
we're thinking it's 100% Sandia copyright.
I would have thought that all the external modules would need to supply
would be the read/write routines. He's got it all in there though? Ugh.

> 
> Should we consider integrating it to use the enfs VFS layer instead?
> It could be written as a module, which when combined with the stackability
> provides naming ontop of a simpler system.

Have to get Celera's needs covered first. That doesn't require a name
space, right? If so, I suggest we defer the topic until we get the 1st
phase for Celera done? I'm not opposed to doing it. I'm just thinking
priorities right now. As well, I'm getting senile, you know, and if we
discuss it now I'll forget :-)

> 
> One thing it does not appear to address is writing the dtree info
> to a store.  That would have to be added before it could be used for
> the naming of a persistent filesystem.

True.

> 
> Trammell
> --
>   o   hu...@sw...                                         O___|
>  /|\  http://www.swcp.com/~hudson/          M 240.476.1373    /\  \_
>  <<   KC5RNF                                H 505.315.5133    \ \/\_\
>   0                                                            U \_  |
> 
> _______________________________________________
> Enfs-devel mailing list
> Enf...@li...
> https://lists.sourceforge.net/lists/listinfo/enfs-devel