At 2:27 PM -0800 3/29/98, Jonathan S. Shapiro wrote:
>There are some "common service" type functions (such as networking)
>that can have a large number of blocking callers. I.e. many domains
>have access to the common service.
>
>Did KeyKOS handle this by pushing the service code back into the
>client where possible, or did it use some techique to manage a large
>number of outstanding resume keys? If the latter, how was this done?
Kernel services had the option of "stalling the caller". To code outside the kernel, it looked like the caller was about to issue the call.
Services built outside the kernel (e.g. the X.25 networking services) built capability structures to save the resume keys.
Bill Frantz | If hate must be my prison | Periwinkle -- Consulting (408)356-8506 | lock, then love must be | 16345 Englewood Ave. frantz@netcom.com | the key. - Phil Ochs | Los Gatos, CA 95032, USA