From: Sunil Kumar Kori <skori@marvell.com>
To: Amit Prakash Shukla <amitprakashs@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Amit Prakash Shukla <amitprakashs@marvell.com>
Subject: RE: [PATCH v2 3/3] examples/l3fwd-graph: add IPv6 lookup and rewrite support
Date: Mon, 22 May 2023 05:49:41 +0000 [thread overview]
Message-ID: <CO6PR18MB38608412EE7F214714A25803B4439@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230518155654.1756576-3-amitprakashs@marvell.com>
Hi Amit,
Please look into build failure.
http://mails.dpdk.org/archives/test-report/2023-May/396241.html
Thanks & Regards
Sunil Kumar Kori
> -----Original Message-----
> From: Amit Prakash Shukla <amitprakashs@marvell.com>
> Sent: Thursday, May 18, 2023 9:27 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Kiran Kumar
> Kokkilagadda <kirankumark@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>
> Cc: dev@dpdk.org; Sunil Kumar Kori <skori@marvell.com>; Amit Prakash
> Shukla <amitprakashs@marvell.com>
> Subject: [PATCH v2 3/3] examples/l3fwd-graph: add IPv6 lookup and rewrite
> support
>
> From: Sunil Kumar Kori <skori@marvell.com>
>
> Similar to ipv4, to support IPv6 lookup and rewrite node routes and rewrite
> data needs to be added.
>
> Patch adds routes for ipv6 to validate ip6_lookup node and rewrite data to
> validate ip6_rewrite node.
>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> ---
> v2:
> - Performance related changes
>
> doc/guides/sample_app_ug/l3_forward_graph.rst | 40 ++++++----
> examples/l3fwd-graph/main.c | 77 ++++++++++++++++++-
> 2 files changed, 98 insertions(+), 19 deletions(-)
>
[snipped]
> 2.25.1
next prev parent reply other threads:[~2023-05-22 5:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:11 [PATCH 1/3] lib: add IPv6 lookup node Amit Prakash Shukla
2023-05-16 9:11 ` [PATCH 2/3] lib: add IPv6 rewrite node Amit Prakash Shukla
2023-05-16 9:11 ` [PATCH 3/3] examples/l3fwd-graph: add IPv6 lookup and rewrite support Amit Prakash Shukla
2023-05-18 15:56 ` [PATCH v2 1/3] lib: add IPv6 lookup node Amit Prakash Shukla
2023-05-18 15:56 ` [PATCH v2 2/3] lib: add IPv6 rewrite node Amit Prakash Shukla
2023-05-18 15:56 ` [PATCH v2 3/3] examples/l3fwd-graph: add IPv6 lookup and rewrite support Amit Prakash Shukla
2023-05-22 5:49 ` Sunil Kumar Kori [this message]
2023-05-29 6:27 ` Sunil Kumar Kori
2023-05-30 8:51 ` [PATCH v2 1/3] lib: add IPv6 lookup node Nithin Dabilpuram
2023-05-31 11:37 ` [PATCH v3 " Amit Prakash Shukla
2023-05-31 11:37 ` [PATCH v3 2/3] lib: add IPv6 rewrite node Amit Prakash Shukla
2023-06-01 2:26 ` Nithin Dabilpuram
2023-06-05 16:29 ` Nithin Dabilpuram
2023-05-31 11:37 ` [PATCH v3 3/3] examples/l3fwd-graph: add IPv6 lookup and rewrite support Amit Prakash Shukla
2023-06-05 16:32 ` Nithin Dabilpuram
2023-06-01 2:24 ` [PATCH v3 1/3] lib: add IPv6 lookup node Nithin Dabilpuram
2023-06-12 17:58 ` [EXT] " Amit Prakash Shukla
2023-06-12 20:14 ` Thomas Monjalon
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=CO6PR18MB38608412EE7F214714A25803B4439@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=amitprakashs@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.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).