[282] in Kerberos
More protocol discussion
daemon@TELECOM.MIT.EDU (Steve Miller)
Tue Dec 8 17:45:31 1987
From: miller%erlang.DEC@DECWRL.DEC.COM (Steve Miller)
To: kerberos@ATHENA.MIT.EDU, MILLER@DECWRL.DEC.COM
Sorry. Fat fingered the editor, didn't think it would send it off.
The point of the redefined requirement is that the calling thread
needs the ability to specify particular routines that block it after the
request has been sent, and unblock it after the response has been received.
Normally, we expect that this is specified at stub generation time or
link time, for example to hook into the ADA run-time threads package.
The architecture does not distinguish between the user and kernel mode
parts of a call. For modeling purposes, assume there is just a single
thread that executes in user and/or kernel mode
until the message is physically on the wire, then blocks. Similarly,
it unblocks as soon as the response is received, and continues executing
to provide the reply arguments, et. al, to the user. The fact that a
real kernel queues requests and has its own internal threads is not
relevant to our architecture.
Steve
