From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <66EC9842-1F95-40F9-8765-E4C948BD2738@vmware.com> References: <66EC9842-1F95-40F9-8765-E4C948BD2738@vmware.com> Date: Tue, 21 Jan 2014 23:14:12 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=e89a8f64352e9beb4104f0832a1e Subject: Re: [9fans] Duplicate fids on 9p server Topicbox-Message-UUID: b426644e-ead8-11e9-9d60-3106f5b1d025 --e89a8f64352e9beb4104f0832a1e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 21 January 2014 23:00, Amol Dixit wrote: > At some point in future, I would like to understand how in the case of > clients sharing a single connection, the =E2=80=9Cagent managing the shar= ing > arranges that no two clients chose the same fid=E2=80=9D. > 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). --e89a8f64352e9beb4104f0832a1e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= 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 o= f clients sharing a single connection, the =E2=80=9Cagent managing the shar= ing arranges that no two clients chose the same fid=E2=80=9D.

In the Plan 9 kernel, one important such agent is the mount drive= r itself (devmnt.c), which converts operations derived from system calls in= to 9P requests.
It relies on the fid in eac= h Chan being unique in the kernel, so when several processes act as 9P clie= nts on a shared connection, the fid space is properly managed
(ie, each client process effectively has its own= fid space).

--e89a8f64352e9beb4104f0832a1e--