9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] qids
Date: Wed, 26 Mar 2003 17:42:54 +0000	[thread overview]
Message-ID: <8536106e05d2ec2c9996c2d623575b2c@vitanuova.com> (raw)

> Servers of original files are encouraged to use only the low 48 bits
> of the qid.path to permit encapsulating servers to use the top 16 bits
> to generate uniqueness.

what about those that encapsulate the encapsulators?

i don't see how this helps much, given that you can't rely
on it. i suppose it reduces the likelyhood that an exportfs-like
service will have to rewrite a file's qid when it's walked to,
and more so if the encapsulating service chooses a random
starting point for those top 16 bits... is that the point?

  rog.



             reply	other threads:[~2003-03-26 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 17:42 rog [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-09 14:30 [9fans] QIDs Steve Simon
2008-01-09 14:52 ` Charles Forsyth
2003-03-26 16:24 [9fans] qids vic
2003-03-26 16:29 ` rob pike, esq.
2003-03-26 17:29   ` Axel Belinfante

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=8536106e05d2ec2c9996c2d623575b2c@vitanuova.com \
    --to=rog@vitanuova.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).