From 0f98bd853e71466b60189d18148d2b4b66c5d238 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 14 Sep 2007 15:31:38 +0200 Subject: Add some more wiki links. --- ipc.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'ipc.mdwn') diff --git a/ipc.mdwn b/ipc.mdwn index a3dda6b3..78d74f33 100644 --- a/ipc.mdwn +++ b/ipc.mdwn @@ -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. -- cgit v1.2.3