9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p vs http
Date: Mon, 15 Nov 2010 15:37:56 +0000	[thread overview]
Message-ID: <AANLkTi=ureiBZ-aRqqXAz3YyB2ynzjoDnx=7SwTpi+NQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinuwotdp-c82xUBshPeDA5i-BjCqmUB5BsabZGZ@mail.gmail.com>

On 15 November 2010 14:15, Gorka Guardiola <paurea@gmail.com> wrote:
> By namespaces I mean qid's , the notion that a file is the same if the
> name isn't.

mind you, that's problematic in 9p. the qid can be the same even if the
file is different:

% ls -lqd /n/dump/2006/0707/usr/rog
(000000000003d540 1122 80) d-rwxr-xr-x M 42850 rog rog 0 Jun  7  2005
/n/dump/2005/0707/usr/rog
% ls -lqd /n/dump/2006/0707/usr/rog
(000000000003d540 1157 80) d-rwxr-xr-x M 42850 rog rog 0 Jun 12  2006
/n/dump/2006/0707/usr/rog

they have the same qid but they're different directories
with different contents.

it's difficult to do a good job when embedding file systems, as the qid space is
fixed. you can cheat, by rewriting the qid when the file is actually opened
to paper over the most obvious problems, but it's still not great.

perhaps things would be easier if qids were sufficiently large (e.g.
sha1 hash sized)
that an embedding file server could make up new qids (or create them by xoring
in other info) without fear of clashes.

re: 9p pipelining - i've been working on a little experiment related
to this. i'll be sharing the
results in a little while.



  reply	other threads:[~2010-11-15 15:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  3:25 Sam Watkins
2010-11-15  4:20 ` John Floren
2010-11-15  4:26   ` Bruce Ellis
2010-11-15  5:16   ` Sam Watkins
2010-11-15  5:26     ` John Floren
2010-11-15 14:09     ` Gorka Guardiola
2010-11-15 14:15       ` Gorka Guardiola
2010-11-15 15:37         ` roger peppe [this message]
2010-11-15 16:45           ` C H Forsyth
2010-11-15 16:37             ` roger peppe
2010-11-15 16:48               ` erik quanstrom
2010-11-15 17:02                 ` roger peppe
2010-11-15 19:29                   ` erik quanstrom
2010-11-15 21:38                     ` roger peppe
2010-11-16  1:18                       ` erik quanstrom
2010-11-16 12:12                         ` roger peppe
2010-11-16 15:56                           ` Charles Forsyth
2010-11-16 16:04                             ` erik quanstrom
2010-11-16 16:32                               ` Charles Forsyth
2010-11-16 17:11                                 ` roger peppe
2010-11-15 15:44 ` David Leimbach
2010-11-15 15:55   ` Venkatesh Srinivas
2010-11-15 15:57     ` David Leimbach
2010-11-15 18:44 ` Russ Cox
2010-11-15 19:00   ` Dan Adkins
2010-11-15 22:18     ` Yaroslav
2010-11-15 22:34       ` erik quanstrom
2010-11-16 12:42     ` Russ Cox

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='AANLkTi=ureiBZ-aRqqXAz3YyB2ynzjoDnx=7SwTpi+NQ@mail.gmail.com' \
    --to=rogpeppe@gmail.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).