From: hugang <linuxbest@soul.com.cn>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RPC vs Socket
Date: Mon, 25 Jun 2001 11:27:56 +0800 [thread overview]
Message-ID: <20010625112756.25c7b81c.linuxbest@soul.com.cn> (raw)
In-Reply-To: <shs66dnryb0.fsf@charged.uio.no>
In-Reply-To: <20010621052321.24581.qmail@nw171.netaddress.usa.net> <20010623160658.A19533@artax.karlin.mff.cuni.cz> <shs66dnryb0.fsf@charged.uio.no>
On 23 Jun 2001 17:49:39 +0200
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> >>>>> " " == Jan Hudec <bulb@ucw.cz> writes:
>
> > Both seem to have pros and cons. RPC should be easier to write
> > (especialy the server side), but it performs bad with UDP on
> > slow links. (NFS did not work on 115200 serial line because of
> > too many dropped packets - TCP flow control too badly needed in
> > such cases). Or can linux do RPC over TCP?
>
> The RPC client code for TCP is ready and already working both in
> 2.2.18+ and 2.4.x.
>
> The server code however needs work.
Where can find some document for write rpc program in kernel .
Thanks
prev parent reply other threads:[~2001-06-25 3:28 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
2001-06-23 14:06 ` Jan Hudec
2001-06-23 15:49 ` Trond Myklebust
2001-06-25 3:27 ` hugang [this message]
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=20010625112756.25c7b81c.linuxbest@soul.com.cn \
--to=linuxbest@soul.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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).