From: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com>
To: kamalakshitha.aligeri@arm.com
Cc: nd@arm.com, stable@dpdk.org,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding
Date: Mon, 14 Nov 2022 21:23:11 +0000 [thread overview]
Message-ID: <20221114212311.2871691-3-kamalakshitha.aligeri@arm.com> (raw)
In-Reply-To: <20221114212311.2871691-1-kamalakshitha.aligeri@arm.com>
LPM based lookup supports both IPv4 and IPv6 forwarding.
Fixes: 6a094e328598 ("examples/l3fwd: implement FIB lookup method")
Cc: stable@dpdk.org
Signed-off-by: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
doc/guides/sample_app_ug/l3_forward.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst
index 94b22da01e..1cc2c1dd1d 100644
--- a/doc/guides/sample_app_ug/l3_forward.rst
+++ b/doc/guides/sample_app_ug/l3_forward.rst
@@ -56,9 +56,8 @@ for the IPv4/IPv6 5-tuple syntax specifically.
The 5-tuple syntax consists of a source IP address, a destination IP address,
a source port, a destination port and a protocol identifier.
-In the sample application, hash-based, FIB-based and ACL-based forwarding supports
+In the sample application, hash-based, LPM-based, FIB-based and ACL-based forwarding supports
both IPv4 and IPv6.
-LPM-based forwarding supports IPv4 only.
During the initialization phase route rules for IPv4 and IPv6 are read from rule files.
Compiling the Application
--
2.17.1
next parent reply other threads:[~2022-11-14 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221114212311.2871691-1-kamalakshitha.aligeri@arm.com>
2022-11-14 21:23 ` Kamalakshitha Aligeri [this message]
[not found] <20221114212533.2871770-1-kamalakshitha.aligeri@arm.com>
2022-11-14 21:25 ` Kamalakshitha Aligeri
2023-03-02 10:11 ` Ruifeng Wang
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=20221114212311.2871691-3-kamalakshitha.aligeri@arm.com \
--to=kamalakshitha.aligeri@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
/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).