From: Gary Wright <gwtmp01@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p2010
Date: Thu, 23 Apr 2009 13:54:32 -0400 [thread overview]
Message-ID: <23ADFC2E-B18A-46DA-A1C1-B14EA6B29EB1@mac.com> (raw)
In-Reply-To: <e6be4507c9b383e1b20cb8d26f3d03ad@quanstro.net>
On Apr 23, 2009, at 12:26 PM, erik quanstrom wrote:
> with 9p2000, if you want to do a Tread, it's pretty clear that
> one needs to read(2); traditiona syscalls map directly to 9p.
It seems to me that the syscall interface is by design different than
the 9p2000 api:
- most syscalls map to a sequence of 9p2000 messages (allocate a new
fid, walk to the named resource, open/stat/remove)
- open files are represented by file descriptors, not 9p2000 fids
- file descriptors map to fids in a n -> 1 relationship
- file descriptors maintain a current offset
- other than fids associated with file descriptors, the only other fid
associated with a process is the current working directory (i.e. you
can't cache the result of a Twalk other than via the current working
directory)
- there is no direct access to Twalk
- the semantics of a process namespace is a non-trivial multiplexing
of several 9p2000 namespaces
I was reading through the source of exportfs the other day and it
struck me that there was quite a bit of work involved in mapping
incoming 9p2000 messages into syscalls within the process namespace
(e.g., fids vs file descriptors, qid clashes).
prev parent reply other threads:[~2009-04-23 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:26 erik quanstrom
2009-04-23 17:22 ` roger peppe
2009-04-23 17:28 ` erik quanstrom
2009-04-23 17:38 ` David Leimbach
2009-04-23 17:31 ` Fco. J. Ballesteros
2009-04-23 17:53 ` roger peppe
2009-04-26 21:29 ` Roman V. Shaposhnik
2009-04-27 7:32 ` roger peppe
2009-04-23 17:55 ` Eric Van Hensbergen
2009-04-23 18:35 ` Steve Simon
2009-04-23 17:54 ` Gary Wright [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=23ADFC2E-B18A-46DA-A1C1-B14EA6B29EB1@mac.com \
--to=gwtmp01@mac.com \
--cc=9fans@9fans.net \
/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).