From 17a983224701dac832e5f2b39cea24ce31ab1da5 Mon Sep 17 00:00:00 2001 From: seantywork Date: Thu, 25 Sep 2025 22:01:00 +0900 Subject: [PATCH] rcu cmap done --- README.md | 2 +- krcu-cmap/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 243ab03..b8865b8 100644 --- a/README.md +++ b/README.md @@ -2125,7 +2125,7 @@ sudo iptables -t nat -A POSTROUTING -o wlo1 -p tcp -j MASQUERADE # outgoing postrouting -sudo iptables -t nat -A POSTROUTING -o wlo1 -p tcp -s 192.168.10.50 -j SNAT 192.168.10.5 +sudo iptables -t nat -A POSTROUTING -o wlo1 -p tcp -s 192.168.10.50 -j SNAT --to-source 192.168.10.5 # permanent rule diff --git a/krcu-cmap/README.md b/krcu-cmap/README.md index 9279655..489fe5a 100644 --- a/krcu-cmap/README.md +++ b/krcu-cmap/README.md @@ -3,13 +3,13 @@ - source: [linuxyz/krcu-cmap](https://github.com/seantywork/linuxyz/tree/main/krcu-cmap) - date: 2509-24 -In user space on Linux, we can utilize pthread_rwlock to design a read-heavy data structure. +In user space on Linux, we can utilize `pthread_rwlock` to design a read-heavy data structure. A similar thing in the Linux kernel space is called `rcu`, a shorthand for "read, copy, update". Full documentation on it is [here](https://www.kernel.org/doc/html/next/RCU/whatisRCU.html) -However, with pthread_rwlock in mind, it could be a little bit puzzling (at least it was for me) \ +However, with `pthread_rwlock` in mind, it could be a little bit puzzling (at least it was for me) \ to grasp the proper use and order of apis unlike in the case of \ pthread_rwlock where you simply call *_rdlock on read and *_wrlock \ on update -- 2.43.0