From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Blesson Paul <blessonpaul@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RPC vs Socket
Date: 21 Jun 2001 15:37:01 +0200 [thread overview]
Message-ID: <shsithqx8ci.fsf@charged.uio.no> (raw)
In-Reply-To: <20010621052321.24581.qmail@nw171.netaddress.usa.net>
In-Reply-To: Blesson Paul's message of "20 Jun 2001 23:23:21 MDT"
>>>>> " " == Blesson Paul <blessonpaul@usa.net> writes:
> hi all
> I am in the way of building a new remote
> file system.
> Presently I decided to use sockets for remote
> communication. Lately I understood that RPC is used in coda and
> nfs file systems(is it so). I want to know the fessibility in
> using RPC in the new file system.
Should be no problem. The RPC layer is not tied to any particular
filesystem.
On the client, you need to set up struct rpc_procinfo with the
necessary RPC XDR routines, which you then declare to the RPC layer
using a struct rpc_program and a call to rpc_create_client(). See
for instance linux/fs/lockd/mon.c, or linux/fs/nfs/mount_clnt.c...
For the server, things are likely to be a bit more complex in that you
need to declare the routines using structs svc_program, svc_version
and rpc_procinfo (again) and then set up a daemon process. Examples of
use include linux/fs/lockd/svc.c and linux/fs/nfsd/nfssvc.c...
Cheers,
Trond
next prev parent reply other threads:[~2001-06-21 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 5:23 RPC vs Socket Blesson Paul
2001-06-21 13:37 ` Trond Myklebust [this message]
2001-06-23 14:06 ` Jan Hudec
2001-06-23 15:49 ` Trond Myklebust
2001-06-25 3:27 ` hugang
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=shsithqx8ci.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=blessonpaul@usa.net \
--cc=linux-kernel@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).