diff options
| -rw-r--r-- | destructive_interference.mdwn (renamed from destructiveinterference.mdwn) | 2 | ||||
| -rw-r--r-- | ipc.mdwn | 8 |
2 files changed, 5 insertions, 5 deletions
diff --git a/destructiveinterference.mdwn b/destructive_interference.mdwn index 227710a7..941da8a4 100644 --- a/destructiveinterference.mdwn +++ b/destructive_interference.mdwn @@ -15,7 +15,7 @@ your rights under copyright, including the rights to copy, modify, and redistribute your contributions. """]] -Interference can be destructive or non-destructive. When a principal +Interference can be destructive or non-destructive. When a [[principal]] invokes an object (thereby requesting a service) and the implementation carries out the principal's intent, the interference was non-destructive in the sense that the interference was desired. @@ -25,12 +25,12 @@ provided by the Unix kernel and Unix is not designed to be [[Microkernel]] systems, on the other hand, are generally composed of many components. As components are separated by their respective -address space boundaries, unlike the kernel, they cannot arbitrarily +[[address_space]] boundaries, unlike the kernel, they cannot arbitrarily examine and modify the caller's state. The advantage is that if the protocol is carefully designed, the callee cannot cause the caller -any [[destructive interference]] thereby removing the need for the +any [[destructive_interference]] thereby removing the need for the caller to [[trust]] the callee thus reducing the former's [[tcb]]. When done systematically, this can increase the system's [[robustness]]. To this end, microkernels provide richer IPC semantics that include -the ability to transfer [[capabilities]] and to use virtual memory -mechanisms to copy data. +the ability to transfer [[capabilities]] and to use [[virtual_memory]] +[[mechanism]]s to copy data. |