Re: [9fans] Why rio instead of 8 1/2

[okamoto@granite.cias.osakafu-u.ac.jp]

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

Thanks Rob!

Now, I got that it shows the state of channel communication.


I got another difficulty to understand how the rio works.
Of course it comes from my personal inablility to read the sources,
however, I suppose it's not so easy to some of Plan 9 users like me, either.

1) all the seven procs have the same memory size, and grows
     coincidently alltogether.  Why?  Only the process of threadmain()
     can grow, can't it?

2) proc wctlproc does only check "New" command, and writectl()
     is called from xfidwrite() which is checked by normal filsyproc().
     So, why /srv/riowctl.$user.$pid is posted?  The "New" command
     can also be checked from the normal filsysproc(), can't it?

3) filsysproc() calls file operation functions in fsys.c, and many of
     those functions call  coresponding xfidxxx functions through
     channel x->c.  Why these two processes are separated?  Or
     what is the merrit to use channel for this purpose, but not just
     function call by pointer alone?

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 1888 bytes --]

From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Why rio instead of 8 1/2
Date: Thu, 13 Jul 2000 19:34:52 -0400
Message-ID: <200007132334.TAA14780@cse.psu.edu>

	Then, No. (2) and (5) procs are marked as rendez.  I looked into
	sources, however, I failed to understand where the No.2 and 5
	processes are called rendezvous.  I know I'm missing something...

They aren't called rendezvous, they're in the rendezvous state.
That field of the ps output is the state of the process, typically a system
call name (such as Wait, Read, etc.) or a process state (Fault, Rendez,
etc.)

-rob