Skip to content

Commit f8e1bce

Browse files
iwashiz0kuba-moo
authored andcommitted
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 <[email protected]> Reviewed-by: Simon Horman <[email protected]> Reviewed-by: Mina Almasry <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
1 parent 66034f7 commit f8e1bce

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

Documentation/networking/devmem.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -256,7 +256,7 @@ Testing
256256
=======
257257

258258
More realistic example code can be found in the kernel source under
259-
``tools/testing/selftests/net/ncdevmem.c``
259+
``tools/testing/selftests/drivers/net/hw/ncdevmem.c``
260260

261261
ncdevmem is a devmem TCP netcat. It works very similarly to netcat, but
262262
receives data directly into a udmabuf.
@@ -268,8 +268,7 @@ ncdevmem has a validation mode as well that expects a repeating pattern of
268268
incoming data and validates it as such. For example, you can launch
269269
ncdevmem on the server by::
270270

271-
ncdevmem -s <server IP> -c <client IP> -f eth1 -d 3 -n 0000:06:00.0 -l \
272-
-p 5201 -v 7
271+
ncdevmem -s <server IP> -c <client IP> -f <ifname> -l -p 5201 -v 7
273272

274273
On client side, use regular netcat to send TX data to ncdevmem process
275274
on the server::

0 commit comments

Comments
 (0)