summaryrefslogtreecommitdiff
path: root/microkernel/mach/port.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'microkernel/mach/port.mdwn')
-rw-r--r--microkernel/mach/port.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/microkernel/mach/port.mdwn b/microkernel/mach/port.mdwn
index 47ef427a..5dcc9ba3 100644
--- a/microkernel/mach/port.mdwn
+++ b/microkernel/mach/port.mdwn
@@ -15,7 +15,7 @@ your rights under copyright, including the rights to copy, modify, and
redistribute your contributions.
"""]]
-Mach ports are [[capabilities]].
+Mach ports are [[capabilities|capability]].
A Mach port is a kernel queue. Each port has associated with
it a receive right and one or more send and send-once rights.
@@ -33,15 +33,15 @@ a single message). Enqueuing a message is equivalent to
[[invoke|invoking]] a capability.
Send and receive rights are named using local names. Each
-task has associated with it a port address space. A ports
+task has associated with it a port [[address_space]]. A ports
are addressed via this table. Each task thus has its own
-private [[NamingContext]] for ports.
+private [[naming_context]] for ports.
-Ports can be [[delegate]]d in an IPC message. When the
+Ports can be [[delegate]]d in an [[IPC]] message. When the
receiver dequeues the message, the right is made available
to it.
-A thread can only block receiving on a single port. To work
+A [[thread]] can only block receiving on a single port. To work
around this, the concept of a port set was introduced. A receive
right can be added to (at most) one port set. When a thread
receives from a port set, it dequeues from any of the ports that