From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Jakub Grajciar <jgrajcia@cisco.com>
Subject: [PATCH 2/5] doc: enhance readability in memif example commands
Date: Thu, 23 Nov 2023 12:44:02 +0100 [thread overview]
Message-ID: <20231123114405.2611371-3-david.marchand@redhat.com> (raw)
In-Reply-To: <20231123114405.2611371-1-david.marchand@redhat.com>
'#.' is a token for ordered lists in RST.
Add a space in those example commands.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
doc/guides/nics/memif.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/guides/nics/memif.rst b/doc/guides/nics/memif.rst
index afc574fdaa..2867b2f66d 100644
--- a/doc/guides/nics/memif.rst
+++ b/doc/guides/nics/memif.rst
@@ -216,15 +216,15 @@ In this example we run two instances of testpmd application and transmit packets
First create ``server`` interface::
- #./<build_dir>/app/dpdk-testpmd -l 0-1 --proc-type=primary --file-prefix=pmd1 --vdev=net_memif,role=server -- -i
+ # ./<build_dir>/app/dpdk-testpmd -l 0-1 --proc-type=primary --file-prefix=pmd1 --vdev=net_memif,role=server -- -i
Now create ``client`` interface (server must be already running so the client will connect)::
- #./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif -- -i
+ # ./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif -- -i
You can also enable ``zero-copy`` on ``client`` interface::
- #./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif,zero-copy=yes --single-file-segments -- -i
+ # ./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif,zero-copy=yes --single-file-segments -- -i
Start forwarding packets::
@@ -260,7 +260,7 @@ To see socket filename use show memif command::
Now create memif interface by running testpmd with these command line options::
- #./dpdk-testpmd --vdev=net_memif,socket=/run/vpp/memif.sock -- -i
+ # ./dpdk-testpmd --vdev=net_memif,socket=/run/vpp/memif.sock -- -i
Testpmd should now create memif client interface and try to connect to server.
In testpmd set forward option to icmpecho and start forwarding::
@@ -283,7 +283,7 @@ The situation is analogous to cross connecting 2 ports of the NIC by cable.
To set the loopback, just use the same socket and id with different roles::
- #./dpdk-testpmd --vdev=net_memif0,role=server,id=0 --vdev=net_memif1,role=client,id=0 -- -i
+ # ./dpdk-testpmd --vdev=net_memif0,role=server,id=0 --vdev=net_memif1,role=client,id=0 -- -i
Then start the communication::
--
2.41.0
next prev parent reply other threads:[~2023-11-23 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 11:44 [PATCH 0/5] Some documentation fixes David Marchand
2023-11-23 11:44 ` [PATCH 1/5] doc: remove restriction on ixgbe vector support David Marchand
2023-11-23 11:45 ` Bruce Richardson
2023-11-23 11:44 ` David Marchand [this message]
2023-11-23 11:48 ` [PATCH 2/5] doc: enhance readability in memif example commands Bruce Richardson
2023-11-23 11:44 ` [PATCH 3/5] doc: fix some ordered lists David Marchand
2023-11-23 11:49 ` Bruce Richardson
2023-11-23 17:22 ` Dariusz Sosnowski
2023-11-24 8:11 ` David Marchand
2023-11-23 11:44 ` [PATCH 4/5] doc: remove number of commands in vDPA guide David Marchand
2023-11-23 12:43 ` Thomas Monjalon
2023-11-23 11:44 ` [PATCH 5/5] doc: use ordered lists David Marchand
2023-11-23 11:53 ` Bruce Richardson
2023-11-23 17:23 ` Dariusz Sosnowski
2023-11-24 12:49 ` [PATCH 0/5] Some documentation fixes David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231123114405.2611371-3-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).