From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] examples/l3fwd: fix compilation issue when using exact-match
Date: Sun, 9 Aug 2015 11:28:45 +0100 [thread overview]
Message-ID: <1439116125-29180-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <1438938514-10304-1-git-send-email-pablo.de.lara.guarch@intel.com>
From: "Pablo de Lara" <pablo.de.lara.guarch@intel.com>
L3fwd was trying to use an inexistent function "simple_ipv6_fwd_4pkts",
instead it should be "simple_ipv6_fwd_8pkts", and "simple_ipv8_fwd_4pkts"
instead of "simple_ipv4_fwd_8pkts".
Fixes: 80fcb4d4 ("examples/l3fwd: increase lookup burst size to 8")
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
---
Changes in v2:
- Missing to fix additional type
examples/l3fwd/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
index 9351322..f113778 100644
--- a/examples/l3fwd/main.c
+++ b/examples/l3fwd/main.c
@@ -1710,11 +1710,11 @@ main_loop(__attribute__((unused)) void *dummy)
& pkts_burst[j+6]->ol_flags
& pkts_burst[j+7]->ol_flags;
if (ol_flag & PKT_RX_IPV4_HDR ) {
- simple_ipv8_fwd_4pkts(&pkts_burst[j],
+ simple_ipv4_fwd_8pkts(&pkts_burst[j],
portid, qconf);
} else if (ol_flag & PKT_RX_IPV6_HDR) {
#endif /* RTE_NEXT_ABI */
- simple_ipv6_fwd_4pkts(&pkts_burst[j],
+ simple_ipv6_fwd_8pkts(&pkts_burst[j],
portid, qconf);
} else {
l3fwd_simple_forward(pkts_burst[j],
--
2.4.2
next prev parent reply other threads:[~2015-08-09 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 9:08 [dpdk-dev] [PATCH] " Pablo de Lara
2015-08-07 10:07 ` Gonzalez Monroy, Sergio
2015-08-09 9:54 ` Thomas Monjalon
2015-08-09 10:28 ` De Lara Guarch, Pablo
2015-08-09 10:28 ` Pablo de Lara [this message]
2015-08-10 16:58 ` [dpdk-dev] [PATCH v2] " 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=1439116125-29180-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.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).