From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Duplicate fids on 9p server
Date: Tue, 21 Jan 2014 23:14:12 +0000 [thread overview]
Message-ID: <CAOw7k5i3cPc5QPZe8USoEBK0aPk2ismfLDtPvgABkZdCHnWWHw@mail.gmail.com> (raw)
In-Reply-To: <66EC9842-1F95-40F9-8765-E4C948BD2738@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On 21 January 2014 23:00, Amol Dixit <amold@vmware.com> wrote:
> At some point in future, I would like to understand how in the case of
> clients sharing a single connection, the “agent managing the sharing
> arranges that no two clients chose the same fid”.
>
In the Plan 9 kernel, one important such agent is the mount driver itself
(devmnt.c), which converts operations derived from system calls into 9P
requests.
It relies on the fid in each Chan being unique in the kernel, so when
several processes act as 9P clients on a shared connection, the fid space
is properly managed
(ie, each client process effectively has its own fid space).
[-- Attachment #2: Type: text/html, Size: 1054 bytes --]
prev parent reply other threads:[~2014-01-21 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 6:49 Amol Dixit
2014-01-20 11:37 ` Charles Forsyth
2014-01-21 23:00 ` Amol Dixit
2014-01-21 23:14 ` Charles Forsyth [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=CAOw7k5i3cPc5QPZe8USoEBK0aPk2ismfLDtPvgABkZdCHnWWHw@mail.gmail.com \
--to=charles.forsyth@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).