From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: [9fans] QIDs
Date: Wed, 9 Jan 2008 14:30:29 +0000 [thread overview]
Message-ID: <0f6c6a7f3fd81c129fc800822f29b4f3@quintile.net> (raw)
beginners question:
Internally in the kernel it matches full QIDs dosn't it?
That is it doesn't compare only the qid.path, so in my
syntetic file server I can differentiate between files
by using a unique-to-me qid.type and then using qid.path
to hold the index of my files in a table?
Seccondly, if I am going to use other bits from qid.type
is there any reccomded practice as to which ones to use
(I assume the lower ones as the upper ones are defined),
however I do rembember somthing about an agregating server
shifting the bits of clients down so they can be combined
uniquely....
Thanks,
-Steve
next reply other threads:[~2008-01-09 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 14:30 Steve Simon [this message]
2008-01-09 14:52 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 17:42 [9fans] qids rog
2003-03-26 16:24 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=0f6c6a7f3fd81c129fc800822f29b4f3@quintile.net \
--to=steve@quintile.net \
--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).