Messages in this thread | | | Subject | Re: structure dentry help... | From | Trond Myklebust <> | Date | 02 Nov 1999 19:16:05 +0100 |
| |
>>>>> Linus Torvalds <torvalds@transmeta.com> writes:
> information fully (like "readdir_long" on NFSv3, I think, and > some other filesystems that just make directories be a list of > inodes directly), then you can just fill in the full inode > information directly and not play games with revalidate.
> Oh. And a final comment - I really don't think the above is > necessarily a good idea. A lot of applications do more > readdir() calls than they ever do lookups, and you might make > readdir() slower by doing the dentry allocation with not enough > gain at lookup time.
Indeed. The latter is the main problem with NFSv3's READDIRPLUS. It's really only useful in the case when you're doing a 'find', but slows things down considerably in all other cases. I'm still looking for a good heuristic before re-enabling it in the current NFSv3 client patches.
Cheers, Trond
- 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/
| |