From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Date: Wed, 6 Feb 2008 09:45:37 +0000 From: Siddhant Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: Subject: [9fans] Re: 9P, procedure calls, kernel, confusion. :( Topicbox-Message-UUID: 48b11894-ead3-11e9-9d60-3106f5b1d025 On Feb 5, 9:36 pm, quans...@quanstro.net (erik quanstrom) wrote: > > see bind(2): > > > Finally, the MCACHE flag, valid for mount only, turns on > > caching for files made available by the mount. By default, > > file contents are always retrieved from the server. With > > caching enabled, the kernel may instead use a local cache to > > satisfy read(5) requests for files accessible through this > > mount point. The currency of cached data for a file is ver- > > ified at each open(5) of the file from this client machine. > > sleezy hacks notwithstanding. > > - erik Thanks people! For your replies! Thanks a lot! I'm new to these kernel thingies. I think I've got the point now. (Almost... :) ) I'll sum it up. Please tell me if I am right or wrong. 9P clients execute remote procedure calls to establish fid in the remote (9P) file server. This fid HAS to get mapped from a channel to a driver in devtab[]. If the file is present in kernel resident filesystem, well and good. Else, mount driver gets in (from devtab[]), converts the local procedure call to a 9P message. (and then the mount driver is supposed to attach a namespace, so it ends there...)