Question on "mappings as cache"

[Stefan Götz]

On Tue, 2003-12-09 at 04:00, Espen Skoglund wrote:
>   5. The region mapper sends a request to the corresponding data space
>      manager.  Note that the request is sent "deceiving" or
>      "propegating", meaning that the address space manager can reply
>      direcly to the faulting thread.
>   6. The data space manager checks if the request is valid and
>      translates the request to a map operation (this translation can
>      be implemented very efficiently).
>   7. The data space manager replies with a mapping to the faulting
>      thread.
>   8. The faulting thread resumes execution.

This protocol is actually an optimization of the following original
protocol which is implemented in SawMill Linux:

5. RM sends non-propagating request and waits for reply
6. DSM checks validity and translates request
7. DSM replies to RM
8. RM replies to faulting thread
9. fautling thread resumes execution

With this protocol, the client does not have to trust the DSM. If the
DSM does not reply (properly), the RM can fix up the faulting thread to
e.g. execute something like a signal handler.

Stefan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20031209/e1043b90/attachment-0001.asc>