From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: fix compilation issue when using exact-match
Date: Sun, 09 Aug 2015 11:54:22 +0200 [thread overview]
Message-ID: <8423022.rae0ANLxGt@xps13> (raw)
In-Reply-To: <1438938514-10304-1-git-send-email-pablo.de.lara.guarch@intel.com>
Hi Pablo,
2015-08-07 10:08, Pablo de Lara:
> L3fwd was trying to use an inexistent function "simple_ipv6_fwd_4pkts",
> instead it should be "simple_ipv6_fwd_8pkts".
>
> Fixes: 80fcb4d4 ("examples/l3fwd: increase lookup burst size to 8")
There are 3 things wrong here.
1/ We must absolutely avoid compile-time paths:
#if (ENABLE_MULTI_BUFFER_OPTIMIZE == 1)
#if (APP_LOOKUP_METHOD == APP_LOOKUP_EXACT_MATCH)
It makes test coverage too hard to track.
2/ When replacing a function, grepping it is a must have.
-simple_ipv6_fwd_4pkts(struct rte_mbuf* m[4], uint8_t portid, struct lcore_conf *qconf)
+simple_ipv6_fwd_8pkts(struct rte_mbuf *m[8], uint8_t portid, struct lcore_conf *qconf)
So this change would be straight forward:
> - simple_ipv6_fwd_4pkts(&pkts_burst[j],
> + simple_ipv6_fwd_8pkts(&pkts_burst[j],
3/ The above commit makes also this wrong replacement:
- simple_ipv4_fwd_4pkts(&pkts_burst[j],
+ simple_ipv8_fwd_4pkts(&pkts_burst[j],
It is still not fixed.
Please send a v2 for this last typo. Thanks
next prev parent reply other threads:[~2015-08-09 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 9:08 Pablo de Lara
2015-08-07 10:07 ` Gonzalez Monroy, Sergio
2015-08-09 9:54 ` Thomas Monjalon [this message]
2015-08-09 10:28 ` De Lara Guarch, Pablo
2015-08-09 10:28 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2015-08-10 16:58 ` Thomas Monjalon
2015-08-10 17:13 ` Thomas Monjalon
2015-08-10 20:39 ` 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=8423022.rae0ANLxGt@xps13 \
--to=thomas.monjalon@6wind.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).