From: Gagandeep Singh <g.singh@nxp.com>
To: dev@dpdk.org
Subject: [v2 0/3] L3fwd changes
Date: Tue, 6 Aug 2024 09:11:17 +0530 [thread overview]
Message-ID: <20240806034120.3165295-1-g.singh@nxp.com> (raw)
In-Reply-To: <20240715101458.645014-1-g.singh@nxp.com>
v2 changes:
* Handled a comment to enhance the invalid port ID logic
and added a user option to decide exit or silently skip
in case invalid port in the rules list.
Gagandeep Singh (3):
examples/l3fwd: support single route file
examples/l3fwd: fix return value on rules add
examples/l3fwd: enhance valid ports checking
examples/l3fwd/em_route_parse.c | 33 ++++++++++--------
examples/l3fwd/l3fwd.h | 16 +++++++++
examples/l3fwd/l3fwd_em.c | 22 ++++++++----
examples/l3fwd/l3fwd_fib.c | 26 +++++++++-----
examples/l3fwd/l3fwd_lpm.c | 26 +++++++++-----
examples/l3fwd/l3fwd_route.h | 2 ++
examples/l3fwd/lpm_route_parse.c | 28 ++++++++-------
examples/l3fwd/main.c | 60 ++++++++++++++++++++++++++------
8 files changed, 154 insertions(+), 59 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2024-08-06 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 10:14 [PATCH 1/3] examples/l3fwd: support single route file Gagandeep Singh
2024-07-15 10:14 ` [PATCH 2/3] examples/l3fwd: fix return value on rules add Gagandeep Singh
2024-07-16 6:55 ` Hemant Agrawal
2024-07-15 10:14 ` [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes Gagandeep Singh
2024-07-17 10:17 ` Konstantin Ananyev
2024-07-18 6:30 ` Gagandeep Singh
2024-07-18 10:01 ` Konstantin Ananyev
2024-07-22 3:28 ` Gagandeep Singh
2024-07-22 4:27 ` Gagandeep Singh
2024-07-23 16:22 ` Konstantin Ananyev
2024-07-24 8:02 ` Konstantin Ananyev
2024-08-02 10:13 ` Gagandeep Singh
2024-08-06 3:41 ` Gagandeep Singh [this message]
2024-08-06 3:41 ` [v2 1/3] examples/l3fwd: support single route file Gagandeep Singh
2024-08-06 3:41 ` [v2 2/3] examples/l3fwd: fix return value on rules add Gagandeep Singh
2024-08-06 3:41 ` [v2 3/3] examples/l3fwd: enhance valid ports checking Gagandeep Singh
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=20240806034120.3165295-1-g.singh@nxp.com \
--to=g.singh@nxp.com \
--cc=dev@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).