rcu cmap done

diff --git a/README.md b/README.md
index 243ab033704ff07e79d8112c24026e7601d5f867..b8865b8e2cace8ebcd1df42cb9a67c7190a66d88 100644 (file)
--- 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 92796550be53803fa4454e47c1211945138243bf..489fe5a5f531df723e37213179e3251081b77799 100644 (file)
--- 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