From: vic <zandy@cs.wisc.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] qids
Date: Wed, 26 Mar 2003 10:24:55 -0600 [thread overview]
Message-ID: <u1dqxfhk.fsf@cs.wisc.edu> (raw)
I am writing a file server to be overlayed on a portion
of an existing name space. It presents the original
name space, plus some new files.
I'm trying to decide how to manage the qids. The issue
is choosing qids for the new files without colliding
with qids of the old ones.
The best related example I've seen is the qid hash
table in exportfs. Is there a better one?
Vic
next reply other threads:[~2003-03-26 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 16:24 vic [this message]
2003-03-26 16:29 ` rob pike, esq.
2003-03-26 17:29 ` Axel Belinfante
2003-03-26 17:42 rog
2008-01-09 14:30 [9fans] QIDs Steve Simon
2008-01-09 14:52 ` Charles Forsyth
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=u1dqxfhk.fsf@cs.wisc.edu \
--to=zandy@cs.wisc.edu \
--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).