Subject: Re: NAMECACHE_ENTER_REVERSE (Re: CVS commit: src/sys/kern)
To: None <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 11/28/2006 20:48:37
In article <20061128194624.95DA811705@yamt.dyndns.org>,
YAMAMOTO Takashi <firstname.lastname@example.org> wrote:
>> Module Name: src
>> Committed By: christos
>> Date: Wed Oct 25 18:56:39 UTC 2006
>> Modified Files:
>> src/sys/kern: vfs_cache.c
>> Log Message:
>> enable namecache enter reverse for linux procfs lookups.
>> XXX: how expensive is that?
>> To generate a diff of this commit:
>> cvs rdiff -r1.65 -r1.66 src/sys/kern/vfs_cache.c
>> Please note that diffs are not public domain; they are subject to the
>> copyright notices on the relevant files.
>it's wrong because our name cache is optional.
>ie. a filesystem is free to choose not to use it at all.
If the filesystem does not implement it, it fails with an error.
Actually I have a good idea how to deal with the failure in the
procfs "exe" case.
>(besides, i don't think it works as linux procfs expects,
>because there entries are not pinned.)
I think it is good enough for the purpose required
(to find any path to the vnode requested).
>if vnode -> name translation is really necessary, it should be
>implemented in upper layers. (caller of VOPs, not filesystems.)
how? can you please elaborate?