[coyotos-dev] constructors, objects, and IDE
clandau at macslab.com
Mon Nov 14 00:24:15 EST 2005
>So, having thought about the 1:1 file:process that you mention Eros has,
No doubt you're aware that EROS is ended, and that CapROS
(http://www.capros.org) and Coyotos are the sucessors.
>I've been wanting to experiment with that and some persistence stuff
>that I've been working on.
CapROS welcomes participation, but neither system currently has
persistence actually working.
>I have a question, though.
>Does the 1:1 hold for physical devices too? For example, is there one
>process per IDE device? i.e.
>Ide_proc_1 == ide(bus=0, dev=0)
>Ide_proc_2 == ide(bus=0, dev=1)
>Ide_proc_3 == ide(bus=1, dev=0)
>Ide_proc_4 == ide(bus=1, dev=1)
>If so, how do you synchronize access to the bus? That is, since devices
>0 and 1 share the same bus, and must not be reading and writing at the
>same time, how do you make sure that's the case? A semaphore would be
>"heavy", perhaps. My thought was that each bus should have it's own
>process, and each device on the bus their own thread.
That is a common design pattern in these systems. One process for
each object (bus, device, etc.), and that process can do any
In CapROS and Coyotos there is no difference between a process and a
thread; we use the term process.
More information about the coyotos-dev