From: dantes@vif.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Network design question
Date: Wed, 9 Jun 2004 00:39:49 -0400 [thread overview]
Message-ID: <40C69495.2020101@vif.com> (raw)
In-Reply-To: <35178.67.85.61.176.1086773361.squirrel@www.infernopark.com>
vdharani@infernopark.com wrote:
>>- from the OSI point of view, the layers 4, 5 and 6 have a custom
>>protocol implementation: 9P.
>
> 9p is similar to nfs protocol. the main difference is nfs is designed to
> serve regular data files and so it treats data in terms of blocks. 9p
> additionally takes care of device files and the data is treated as
> messages of variable size (max is 8192). and 9p messages are not cached.
Isn't it a bit more than NFS? From "The Organisation of Networks in Plan
9", it seems it can also *do* messages and RPC, while AFAIK NFS is
*using* messages and SUN RPC... Maybe I'm just plain wrong.
>>- 9P offers an interface at layer 5 (messages, local)
>>
>>- 9P offers an interface at layer 6 (RPC, local)
>
> i am not sure if 9p can be treated like this. i guess it is pretty much
> the 4 layer tcp/ip with 9p sitting on top of tcp/ip. 9p is like nfs
> protocol and uses rpc mechanism.
Considering from your next answer that IL is a transfer protocol, can 9P
be fully used on top of IL? (ie does it rely exclusively on TCP and its
stream orientation?)
>>- a service does translation from 9P to TCP for external communication
>>(at level 4?).
>>
>>Where does IL fit in all this?
>
> il is pretty much similar to tcp except that while tcp works in
> byte-stream mode, il wrok in message-mode.
OK, thanks for this input.
> thanks
> dharani
Thanks a lot
Jef
prev parent reply other threads:[~2004-06-09 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 3:57 dantes
2004-06-09 9:29 ` vdharani
2004-06-09 4:39 ` dantes [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=40C69495.2020101@vif.com \
--to=dantes@vif.com \
--cc=9fans@cse.psu.edu \
/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).