From: Ibtisam Tariq <ibtisam.tariq@emumba.com>
To: konstantin.ananyev@intel.com
Cc: dev@dpdk.org, Ibtisam Tariq <ibtisam.tariq@emumba.com>,
bernard.iremonger@intel.com
Subject: [dpdk-dev] [PATCH] doc: fix typing error in example/l3_forward_access_ctrl
Date: Mon, 2 Nov 2020 11:19:15 +0000 [thread overview]
Message-ID: <20201102111915.5279-1-ibtisam.tariq@emumba.com> (raw)
Add "--" and remove extra spaces in l3fwd-acl commands.
Fixes: d0dff9ba4 ("doc: sample application user guide")
Cc: bernard.iremonger@intel.com
Signed-off-by: Ibtisam Tariq <ibtisam.tariq@emumba.com>
---
doc/guides/sample_app_ug/l3_forward_access_ctrl.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst b/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst
index 4a96800ec..3cdfbfb17 100644
--- a/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst
+++ b/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst
@@ -236,7 +236,7 @@ The application has a number of command line options:
.. code-block:: console
- ./<build_dir>/examples/dpdk-l3fwd-acl [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] --rule_ipv4 FILENAME rule_ipv6 FILENAME [--alg=<val>] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] [--eth-dest=X,MM:MM:MM:MM:MM:MM]
+ ./<build_dir>/examples/dpdk-l3fwd-acl [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] --rule_ipv4 FILENAME --rule_ipv6 FILENAME [--alg=<val>] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] [--eth-dest=X,MM:MM:MM:MM:MM:MM]
where,
@@ -271,7 +271,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s
.. code-block:: console
- ./<build_dir>/examples/dpdk-l3fwd-acl -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" --rule_ipv4="./rule_ipv4.db" -- rule_ipv6="./rule_ipv6.db" --alg=scalar
+ ./<build_dir>/examples/dpdk-l3fwd-acl -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" --rule_ipv4="./rule_ipv4.db" --rule_ipv6="./rule_ipv6.db" --alg=scalar
In this command:
@@ -293,9 +293,9 @@ In this command:
| | | | |
+----------+------------+-----------+-------------------------------------+
-* The --rule_ipv4 option specifies the reading of IPv4 rules sets from the ./ rule_ipv4.db file.
+* The --rule_ipv4 option specifies the reading of IPv4 rules sets from the ./rule_ipv4.db file.
-* The --rule_ipv6 option specifies the reading of IPv6 rules sets from the ./ rule_ipv6.db file.
+* The --rule_ipv6 option specifies the reading of IPv6 rules sets from the ./rule_ipv6.db file.
* The --alg=scalar option specifies the performing of rule lookup with a scalar function.
--
2.17.1
next reply other threads:[~2020-11-02 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 11:19 Ibtisam Tariq [this message]
2020-11-05 8:54 ` David Marchand
2020-11-20 12:04 ` David Marchand
2020-11-24 12:40 ` Ibtisam Tariq
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=20201102111915.5279-1-ibtisam.tariq@emumba.com \
--to=ibtisam.tariq@emumba.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
/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).