From f8e1bcec62efbce2c6acd116b1f4a82a8441ce11 Mon Sep 17 00:00:00 2001 From: Yui Washizu Date: Tue, 18 Mar 2025 15:12:41 +0900 Subject: [PATCH] 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 Reviewed-by: Simon Horman Reviewed-by: Mina Almasry Link: https://patch.msgid.link/20250318061251.775191-1-yui.washidu@gmail.com Signed-off-by: Jakub Kicinski --- 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 -c -f eth1 -d 3 -n 0000:06:00.0 -l \ - -p 5201 -v 7 + ncdevmem -s -c -f -l -p 5201 -v 7 On client side, use regular netcat to send TX data to ncdevmem process on the server:: -- 2.50.1