summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2018-11-27 22:17:15 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2018-11-27 22:17:15 +0100
commit920b6eebb17e73ea85ecda92adfba196686886af (patch)
tree5b3216dc1e8420fc698c8b45abdce65dc4b79dd2
parentbc652bac4ffedfb0444100a027727a5ea9dcee75 (diff)
Fix some details on RPCs
-rw-r--r--rpc.mdwn7
1 files changed, 3 insertions, 4 deletions
diff --git a/rpc.mdwn b/rpc.mdwn
index 7db5f10..e58f005 100644
--- a/rpc.mdwn
+++ b/rpc.mdwn
@@ -14,13 +14,12 @@ communicating with another userspace process. For example, a user may use
emacs to open a text file for editing. On the Hurd, glibc turns the C function
call into appropriate RPC calls to ext2fs. It is important to remember that
gnumach's IPC facilitates this communication between emacs and ext2fs (with
-the gnumach mach_msg () syscall: one to send the message and one to receive
-the reply).
+the gnumach mach_msg () syscall).
It is also important to distinguish an RPC from a [[system call|system_call]].
-A system call, happens when a userspace process requests something of the kernel.
+A system call is always a userspace process requesting something from the kernel.
An RPC is generally one userspace process requesting something from another
-userspace process.
+userspace process, but it can also be from the kernel. Devices, for instance, can live both in the kernel or in userspace processes, RPCs are used to discuss with them in both cases.