From: Matthew Wilcox <matthew@wil.cx>
To: UZAIR LAKHANI <uzairr_bs1b@yahoo.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Communicating FileSystem Structures b/w Two Machines
Date: Mon, 10 Apr 2006 07:32:57 -0600 [thread overview]
Message-ID: <20060410133257.GD9955@parisc-linux.org> (raw)
In-Reply-To: <20060410061146.89260.qmail@web37915.mail.mud.yahoo.com>
On Sun, Apr 09, 2006 at 11:11:46PM -0700, UZAIR LAKHANI wrote:
> I am in the process of making a filesystem in a
> client/server environment where there is a single
> server having a storage attached and 2 to 3 clients
> accessing that storage through a communication
> mechanism. The client and server are using a
> buffer(unsigned char array) to communicate.
>
> In order for client and server to communicate, they
> have to exchange different structures like
> super-block, inode, dentry, vfsmount etc.
Why on earth do you think that? Certainly you have to communicate
file data and metadata, but why on earth would you ship dentries from
one machine to another? This will never work.
You should probably look at how other network filesystems are designed,
starting with NFS: http://www.faqs.org/rfcs/rfc1094.html
What are your research goals for this new filesystem? Why will it be
any better than OCFS2, NFS (v2 or v4), SMBFS/CIFS, NCPFS, Coda or AFS?
Why don't you start by taking one of these filesystems and modify or
extend it to suit your needs rather than starting from scratch?
next prev parent reply other threads:[~2006-04-10 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 6:11 Communicating FileSystem Structures b/w Two Machines UZAIR LAKHANI
2006-04-10 11:16 ` Martin Jambor
2006-04-10 13:32 ` Matthew Wilcox [this message]
2006-04-11 10:00 ` 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=20060410133257.GD9955@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-fsdevel@vger.kernel.org \
--cc=uzairr_bs1b@yahoo.com \
/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