Re: Regarding a Simple Version of nfs & nfsd (RPC ISSUES)

["Fawad Lateef" <fawadlateef@gmail.com>]

On 3/24/06, UZAIR LAKHANI <uzairr_bs1b@yahoo.com> wrote:
> Hello All,
>
> Thank you Avishay Traeger and Fawad Lateef for having
> a long discussion on my first mail.
>
> Now I try to explain my own design.
>
> Client FS -> read -> sys_read -> vfs_read ->
> wrapper_fs_read -> RPC ... -> server_read
>
> In the above design the client fs is a dummy fs which
> only mimics a fs and passes requests to the wrapper fs
> which by using RPC passes the requests to the server
> which is a actual fs.
>

I don't think your design is feasible Client FS will is the one which
gets request from VFS layer as user issues read which goes to sys_read
and then to vfs_read which in tern call your Client FS function for
reading and from here the request goes to server_read (can be through
RPC) which will act like a wrapper_fs_read and get the data from the
original FS and provide that back to the remote Client FS :) So the
architecture looking fine to me is like this:

User -> sys_read -> vfs_read -> client_fs_read -> RPC ->
wrapper_fs/server_fs_read -> underlying_fs_read -> storage


--
Fawad Lateef