[libc-commits] [libc] [libc][gpu][docs] Fix typos in GPU libc's documentation (PR #138565)
Howard Chu via libc-commits
libc-commits at lists.llvm.org
Mon May 5 12:02:27 PDT 2025
https://github.com/Sberm updated https://github.com/llvm/llvm-project/pull/138565
>From c292a456db411f89b7e74d9a381820d12822632e Mon Sep 17 00:00:00 2001
From: Howard Chu <howardchu95 at gmail.com>
Date: Mon, 5 May 2025 10:41:45 -0700
Subject: [PATCH] [libc][gpu][docs] Fix typos in GPU libc's documentation
Fix typos in GPU libc's documentation about the rpc implementation.
---
libc/docs/gpu/rpc.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libc/docs/gpu/rpc.rst b/libc/docs/gpu/rpc.rst
index 1d6aaea2adcfe..4ac3786cfa085 100644
--- a/libc/docs/gpu/rpc.rst
+++ b/libc/docs/gpu/rpc.rst
@@ -20,8 +20,8 @@ operating system while executing on a GPU.
We implemented remote procedure calls using unified virtual memory to create a
shared communicate channel between the two processes. This memory is often
pinned memory that can be accessed asynchronously and atomically by multiple
-processes simultaneously. This supports means that we can simply provide mutual
-exclusion on a shared better to swap work back and forth between the host system
+processes simultaneously. This support means that we can simply provide mutual
+exclusion on a shared buffer to swap work back and forth between the host system
and the GPU. We can then use this to create a simple client-server protocol
using this shared memory.
@@ -39,7 +39,7 @@ In order to make this transmission channel thread-safe, we abstract ownership of
the given mailbox pair and buffer around a port, effectively acting as a lock
and an index into the allocated buffer slice. The server and device have
independent locks around the given port. In this scheme, the buffer can be used
-to communicate intent and data generically with the server. We them simply
+to communicate intent and data generically with the server. We then simply
provide multiple copies of this protocol and expose them as multiple ports.
If this were simply a standard CPU system, this would be sufficient. However,
More information about the libc-commits
mailing list