• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• [ Next ]In reply to: Jonathan Shapiro Next in thread: Jonathan Shapiro

>KeyKOS does not directly support locks; it is assumed that processes
>needing a semaphore will implement it in shared memory using the
>native instruction set. Having the kernel rescind locks raises some
>bad semantic issues.

The invocation semantics in KeyKOS include locking directly. When two messages are sent to a domain, the domain receives one and the other waits. This seems like locking to me, and can be used to implement pretty much any other sequential synchronization construct. Does KeyKOS specify fairness for domains waiting on a key invocation?

dean

• [ Next ]In reply to: Jonathan Shapiro Next in thread: Jonathan Shapiro