From 5ab3b18865eb813d433a6c0687dfa1f62a1b6055 Mon Sep 17 00:00:00 2001 From: Jon Santmyer Date: Fri, 9 Oct 2026 16:50:13 -0400 Subject: add ipc send/recv mechanism for kernel objects. --- doc/syscall.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/syscall.md b/doc/syscall.md index 1e03425..53626c8 100644 --- a/doc/syscall.md +++ b/doc/syscall.md @@ -305,9 +305,9 @@ If blocking timeout is zero, then the process will wait for the destination proc If the blocking timeout is non-zero, then the process will wait for the destination process to recieve the object for the specified number of scheduler ticks. -| Data | Destination Process | Blocking Timeout | Send Path Length | Send Path | -|--------------|---------------------|-------------------|------------------|----------------------| -| Size (bytes) | sizeof(pid_t) | sizeof(uintmax_t) | 2 | 2 * send_path_length | +| Data | Destination Process | Blocking Timeout | Send Path Length | Send Path | +|--------------|---------------------|-------------------|------------------------|-------------------------------------------| +| Size (bytes) | sizeof(pid_t) | sizeof(uintmax_t) | sizeof(objpath_part_t) | sizeof(objpath_part_t) * send_path_length | While the object is being sent, the kernel will lock the object and copy a pointer to it into the send mailbox. -- cgit v1.2.3