From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org, bruce.richardson@intel.com, pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [PATCH 0/2] l2fwd/l3fwd: rework long options parsing
Date: Tue, 22 Nov 2016 14:52:14 +0100 [thread overview]
Message-ID: <1479822736-32399-1-git-send-email-olivier.matz@6wind.com> (raw)
These 2 patches were part of this RFC, which will not be integrated:
http://dpdk.org/ml/archives/dev/2016-September/046974.html
It does not bring any functional change, it just reworks the way long
options are parsed in l2fwd and l3fwd to avoid uneeded strcmp() calls
and to ease the addition of a new long option in the future.
I send them in case maintainers think it is better this way, but I have
no real need.
Olivier Matz (2):
l3fwd: rework long options parsing
l2fwd: rework long options parsing
examples/l2fwd/main.c | 30 +++++++--
examples/l3fwd/main.c | 169 ++++++++++++++++++++++++++------------------------
2 files changed, 111 insertions(+), 88 deletions(-)
--
2.8.1
next reply other threads:[~2016-11-22 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 13:52 Olivier Matz [this message]
2016-11-22 13:52 ` [dpdk-dev] [PATCH 1/2] l3fwd: " Olivier Matz
2016-11-22 13:52 ` [dpdk-dev] [PATCH 2/2] l2fwd: " Olivier Matz
2016-11-22 13:59 ` [dpdk-dev] [PATCH 0/2] l2fwd/l3fwd: " Olivier Matz
2017-01-17 17:11 ` 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=1479822736-32399-1-git-send-email-olivier.matz@6wind.com \
--to=olivier.matz@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).