9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design clairvoyance & the 9 way
Date: Thu,  8 May 2003 11:41:58 -0400	[thread overview]
Message-ID: <2d47347353bfadb65915218426041e72@plan9.bell-labs.com> (raw)
In-Reply-To: <eaf8e1257d172b0cad6782c630a10bfb@plan9.bell-labs.com>

Dave Mazieres had a reasonable take on the name space.  The
implementation in the kernel (chan.c) is hard to understand.
Exportfs is wierd because the namespace it exports isn't
really what it sees (a bunch of different mount points all
with their own qid space) but instead makes up a new qid
space to paper over the differences.

He wanted to make the name space even more visible, make
the file protocol recursive (i.e. able to encapsulate in
a visible way subsets of itself), and perhaps implement the
whole thing at user level.

I didn't really like his particular solution in that direction
but I believe that his observation was right.  I'm just not sure
what the fix should be or even if it wouldn't be worse than the
problem.


  reply	other threads:[~2003-05-08 15:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 15:33 jmk
2003-05-08 15:41 ` David Presotto [this message]
2003-05-08 16:21   ` rog
2003-05-08 16:27     ` Russ Cox
2003-05-08 16:52       ` rog
2003-05-08 16:25   ` Russ Cox
2003-05-08 17:45     ` rog
2003-05-08 18:33       ` Russ Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-05-07 16:32 C (Was: [9fans] same functions everywhere) northern snowfall
2003-05-07 16:33 ` [9fans] design clairvoyance & the 9 way Sam
2003-05-07 17:34   ` Fco.J.Ballesteros
2003-05-07 20:01   ` David Presotto
2003-05-07 20:34     ` Stephen Wynne
2003-05-07 21:57       ` Steve Kotsopoulos
2003-05-08  4:14       ` A.S. Kukhar
2003-05-08 17:04       ` Dan Cross
2003-05-09 19:14         ` boyd, rounin
2003-05-07 22:33     ` Sam
2003-05-08  0:46       ` northern snowfall
2003-05-08 16:04         ` Sam
2003-05-08 17:08           ` Russ Cox
2003-05-09  1:12           ` Geoff Collyer
2003-05-08 17:26         ` Dan Cross
2003-05-09  1:12           ` northern snowfall
2003-05-09  0:49             ` Dan Cross
2003-05-09  1:07               ` Joel Salomon
2003-05-09  2:53                 ` ron minnich
2003-05-09  8:36                 ` Douglas A. Gwyn
2003-05-09 14:29                   ` ron minnich
2003-05-09 15:41                     ` northern snowfall
2003-05-09  2:18               ` northern snowfall
2003-05-09  7:55         ` Taj Khattra
2003-05-09  9:48           ` northern snowfall
2003-05-09 19:52             ` boyd, rounin
2003-05-09 20:47               ` David Presotto
2003-05-10  2:56                 ` boyd, rounin
2003-05-14 18:55             ` boyd, rounin
2003-05-08  4:04       ` Russ Cox
2003-05-08  0:20   ` northern snowfall
2003-05-19  9:46   ` boyd, rounin

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=2d47347353bfadb65915218426041e72@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --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).