From: UZAIR LAKHANI <uzairr_bs1b@yahoo.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: Regarding a Simple Version of nfs & nfsd (RPC ISSUES)
Date: Fri, 24 Mar 2006 02:37:03 -0800 (PST) [thread overview]
Message-ID: <20060324103703.18778.qmail@web37915.mail.mud.yahoo.com> (raw)
In-Reply-To: <1e62d1370603210753l4630e13ep9f14a41d7b4bc2b3@mail.gmail.com>
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 am not considering overheads or performance issues
now.
Thanks,
Uzair Lakhani,
Karachi, Pakistan.
--- Fawad Lateef <fawadlateef@gmail.com> wrote:
> On 3/21/06, Avishay Traeger <atraeger@cs.sunysb.edu>
> wrote:
> > On Tue, 2006-03-21 at 20:27 +0500, Fawad Lateef
> wrote:
> > > Let me re-draw the diagram you mentioned with my
> idea. The ascii art :)
> > >
> > > Client Side
> > > |
> > > sys_read
> > > |
> > > vfs
> > > |
> > > client fs ................... The fs running
> on client side, doing
> > > nothing by itself, but provide support of
> mounting/unmounting,
> > > readin/writing etc to client os
> > > |
> > > LAN
> > > |
> > > stackable fs .......... or you can say server
> daemon (accessing the real fs)
> > > |
> > > vfs
> > > |
> > > ext2
> > >
> > > I hope now I able to make you clear my idea. Or
> you can suggest any
> > > better than this. (I am just interested, not
> going to make this kind
> > > of FS as don't have time. But your idea might
> help the person asking
> > > question (Uzair))
> >
> > OK. In the original e-mail, I believe the idea
> was to use stackable
> > file systems for both the client and the server.
> In your design, you
> > only use it for the server, so I guess you agree
> with me that using it
> > on the client would be pointless. And as we
> agreed earlier, using it on
> > the server isn't such a good idea either, as you
> will need to throw out
> > almost all of the code.
> >
>
> Yes 100% agreed :) Now as I know your are good in
> file-system side, so
> it will be good if you suggest some better or same
> idea along-with
> some code examples (or some projects on something
> similar) for others
> :)
>
> --
> Fawad Lateef
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-03-24 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 4:18 Regarding a Simple Version of nfs & nfsd UZAIR LAKHANI
2006-03-20 23:10 ` Avishay Traeger
2006-03-21 9:09 ` Fawad Lateef
2006-03-21 13:06 ` Avishay Traeger
2006-03-21 13:33 ` Fawad Lateef
2006-03-21 15:09 ` Avishay Traeger
2006-03-21 15:27 ` Fawad Lateef
2006-03-21 15:40 ` Avishay Traeger
2006-03-21 15:53 ` Fawad Lateef
2006-03-24 10:37 ` UZAIR LAKHANI [this message]
2006-03-26 7:46 ` Regarding a Simple Version of nfs & nfsd (RPC ISSUES) Fawad Lateef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060324103703.18778.qmail@web37915.mail.mud.yahoo.com \
--to=uzairr_bs1b@yahoo.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).