From bc652bac4ffedfb0444100a027727a5ea9dcee75 Mon Sep 17 00:00:00 2001 From: Joshua Branson Date: Mon, 26 Nov 2018 11:51:44 -0500 Subject: I added mach_msg to the gnumach syscall page. I tried to add some more information to the rpc and syscall pages. --- rpc.mdwn | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'rpc.mdwn') diff --git a/rpc.mdwn b/rpc.mdwn index 5fed0aa2..7db5f103 100644 --- a/rpc.mdwn +++ b/rpc.mdwn @@ -9,7 +9,20 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -RPC stands for remote procedure call. +RPC stands for remote procedure call. It is generally one userspace processes +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). + +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. +An RPC is generally one userspace process requesting something from another +userspace process. + + # See Also -- cgit v1.2.3