From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Qid path generation
Date: Mon, 5 May 2003 23:05:48 -0400 [thread overview]
Message-ID: <f4fff663210dfebf3b67ca95a69874a2@plan9.bell-labs.com> (raw)
In-Reply-To: <b4460a1b789c3d712983b272f0488dbb@plan9.bell-labs.com>
The 64-bit hash for qids is a good idea
except that exportfs and programs like it assume that
the top 16 bits are fairly low entropy so they can be
renamed as necessary to present many 9P servers
to a single client. Taking 48 bits of it will give you
2^24, which is halfway between the two and might
be enough to appease both camps.
Russ
prev parent reply other threads:[~2003-05-06 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 21:29 Andrew Simmons
2003-05-05 21:30 ` W. Josephson
2003-05-05 21:33 ` rsc
2003-05-05 21:45 ` Andrew Simmons
2003-05-06 11:29 ` Aharon Robbins
2003-05-06 1:09 ` David Presotto
2003-05-06 1:10 ` David Presotto
2003-05-06 1:23 ` Andrew Simmons
2003-05-06 2:29 ` David Presotto
2003-05-06 3:05 ` Russ Cox [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=f4fff663210dfebf3b67ca95a69874a2@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).