[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250318061251.775191-1-yui.washidu@gmail.com>
Date: Tue, 18 Mar 2025 15:12:41 +0900
From: Yui Washizu <yui.washidu@...il.com>
To: davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
horms@...nel.org,
corbet@....net,
almasrymina@...gle.com,
sdf@...ichev.me
Cc: Yui Washizu <yui.washidu@...il.com>,
linux-doc@...r.kernel.org,
netdev@...r.kernel.org
Subject: [PATCH net-next] docs: fix the path of example code and example commands for device memory TCP
This updates the old path and fixes the description of unavailable options.
Signed-off-by: Yui Washizu <yui.washidu@...il.com>
---
Documentation/networking/devmem.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/devmem.rst b/Documentation/networking/devmem.rst
index d95363645331..eb678ca45496 100644
--- a/Documentation/networking/devmem.rst
+++ b/Documentation/networking/devmem.rst
@@ -256,7 +256,7 @@ Testing
=======
More realistic example code can be found in the kernel source under
-``tools/testing/selftests/net/ncdevmem.c``
+``tools/testing/selftests/drivers/net/hw/ncdevmem.c``
ncdevmem is a devmem TCP netcat. It works very similarly to netcat, but
receives data directly into a udmabuf.
@@ -268,8 +268,7 @@ ncdevmem has a validation mode as well that expects a repeating pattern of
incoming data and validates it as such. For example, you can launch
ncdevmem on the server by::
- ncdevmem -s <server IP> -c <client IP> -f eth1 -d 3 -n 0000:06:00.0 -l \
- -p 5201 -v 7
+ ncdevmem -s <server IP> -c <client IP> -f <ifname> -l -p 5201 -v 7
On client side, use regular netcat to send TX data to ncdevmem process
on the server::
--
2.43.5
Powered by blists - more mailing lists