* [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding [not found] <20221114212533.2871770-1-kamalakshitha.aligeri@arm.com> @ 2022-11-14 21:25 ` Kamalakshitha Aligeri 2023-03-02 10:11 ` Ruifeng Wang 0 siblings, 1 reply; 3+ messages in thread From: Kamalakshitha Aligeri @ 2022-11-14 21:25 UTC (permalink / raw) To: jerinj, thomas, david.marchand Cc: dev, nd, Kamalakshitha Aligeri, stable, Honnappa Nagarahalli 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding 2022-11-14 21:25 ` [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding Kamalakshitha Aligeri @ 2023-03-02 10:11 ` Ruifeng Wang 0 siblings, 0 replies; 3+ messages in thread From: Ruifeng Wang @ 2023-03-02 10:11 UTC (permalink / raw) To: Kamalakshitha Aligeri, jerinj, thomas, david.marchand Cc: dev, nd, Kamalakshitha Aligeri, stable, Honnappa Nagarahalli, nd > -----Original Message----- > From: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com> > Sent: Tuesday, November 15, 2022 5:26 AM > To: jerinj@marvell.com; thomas@monjalon.net; david.marchand@redhat.com > Cc: dev@dpdk.org; nd <nd@arm.com>; Kamalakshitha Aligeri <Kamalakshitha.Aligeri@arm.com>; > stable@dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> > Subject: [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding > > 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 Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <20221114212311.2871691-1-kamalakshitha.aligeri@arm.com>]
* [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding [not found] <20221114212311.2871691-1-kamalakshitha.aligeri@arm.com> @ 2022-11-14 21:23 ` Kamalakshitha Aligeri 0 siblings, 0 replies; 3+ messages in thread From: Kamalakshitha Aligeri @ 2022-11-14 21:23 UTC (permalink / raw) To: kamalakshitha.aligeri; +Cc: nd, stable, Honnappa Nagarahalli 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-03-02 10:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20221114212533.2871770-1-kamalakshitha.aligeri@arm.com>
2022-11-14 21:25 ` [PATCH 3/3] doc/l3fwd: lpm supports IPv4 and IPv6 forwarding Kamalakshitha Aligeri
2023-03-02 10:11 ` Ruifeng Wang
[not found] <20221114212311.2871691-1-kamalakshitha.aligeri@arm.com>
2022-11-14 21:23 ` Kamalakshitha Aligeri
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).