Re: Some more questions about Reiser4 ;)

[Hans Reiser <reiser@namesys.com>]

Fred -- Speed Up -- wrote:

>>>The reason why I asked this was because I didn't knew that VFS was the
>>>      
>>>
>one
>  
>
>>>and only responsible for the path resolving ;)
>>>
>>>      
>>>
>>That is too strong a statement.  VFS delegates parts of the task to us,
>>particularly directory lookup.
>>    
>>
>But VFS wants the directory reading task to return a list of files with
>corresponding inodes numbers. Reiser4, in this case, has to check out the
>tree and read the directory entries, but what about resolving a simple file
>path : does VFS in this case want the files and subdirectory listings of
>every directory the path consists in, or does VFS directly ask Reiser4 to
>resolve the whole path ?
>What does Reiser4 do to improve the path resolving and directory listing
>performance ? Do you implement another cache even if the VFS allready got
>one ?
>
You are right.  It is a problem.  It is a problem we have sidestepped 
for a long time, but sometime in the next 5 years we will have to step 
into that code and regut VFS, and this will probably coincide with us 
introducing dramatic upwardly compatible changes in the semantics.

>
>  
>
>>Elena, can you draw a diagram or somehow document the disk layout for
>>reiser4.  We seem to describe the pieces but not the whole.
>>    
>>
>That would be a great thing ;)
>
>
>Thank you for all your previous answers ... M. Reiser ;)
>
>Fred
>
>
>
>  
>


-- 
Hans