From: Yuanhan Liu <yliu@fridaylinux.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] patch 'examples/qos_sched: fix build for less lcores' has been queued to LTS release 16.11.3
Date: Mon, 24 Jul 2017 03:07:31 +0800 [thread overview]
Message-ID: <1500836852-3563-6-git-send-email-yliu@fridaylinux.org> (raw)
In-Reply-To: <1500836852-3563-1-git-send-email-yliu@fridaylinux.org>
Hi,
FYI, your patch has been queued to LTS release 16.11.3
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 07/27/17. So please
shout if anyone has objections.
Thanks.
--yliu
---
>From 37d6029ba728edffd7ff05b9c0d2a5fad4219241 Mon Sep 17 00:00:00 2001
From: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wed, 19 Jul 2017 13:43:10 +0530
Subject: [PATCH] examples/qos_sched: fix build for less lcores
[ upstream commit e481ebfd622c23a1d854cb4655a3534d68d322af ]
APP_MAX_LCORES is hardcoded as 64.
This will cause build err when RTE_MAX_LCORE is less then 64.
"args.c:127:22: error: iteration 8 invokes undefined behavior
[-Werror=aggressive-loop-optimizations]
if (cfg->lcore_role[i] == ROLE_RTE)
~~~~~~~~~~~~~~~^~~
args.c:126:2: note: within this loop
for (i = 0; i < APP_MAX_LCORE; i++) {"
Fixes: d52b5e735aa3 ("examples/qos_sched: fix lcore limit")
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
examples/qos_sched/main.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/examples/qos_sched/main.h b/examples/qos_sched/main.h
index c7490c6..8d02e1a 100644
--- a/examples/qos_sched/main.h
+++ b/examples/qos_sched/main.h
@@ -69,8 +69,13 @@ extern "C" {
#define BURST_TX_DRAIN_US 100
#ifndef APP_MAX_LCORE
+#if (RTE_MAX_LCORE > 64)
#define APP_MAX_LCORE 64
+#else
+#define APP_MAX_LCORE RTE_MAX_LCORE
+#endif
#endif
+
#define MAX_DATA_STREAMS (APP_MAX_LCORE/2)
#define MAX_SCHED_SUBPORTS 8
#define MAX_SCHED_PIPES 4096
--
2.7.4
next prev parent reply other threads:[~2017-07-23 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 19:07 [dpdk-stable] patch 'mbuf: fix VXLAN port in comment' " Yuanhan Liu
2017-07-23 19:07 ` [dpdk-stable] patch 'net/e1000: fix LSC interrupt' " Yuanhan Liu
2017-07-23 19:07 ` [dpdk-stable] patch 'net/i40e: fix ethertype filter for new FW' " Yuanhan Liu
2017-07-23 19:07 ` [dpdk-stable] patch 'net/ixgbe: fix Rx/Tx queue interrupt for x550 devices' " Yuanhan Liu
2017-07-23 19:07 ` [dpdk-stable] patch 'crypto/qat: fix NULL authentication hang' " Yuanhan Liu
2017-07-23 19:07 ` Yuanhan Liu [this message]
2017-07-23 19:07 ` [dpdk-stable] patch 'examples/l2fwd-crypto: fix padding' " Yuanhan Liu
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=1500836852-3563-6-git-send-email-yliu@fridaylinux.org \
--to=yliu@fridaylinux.org \
--cc=hemant.agrawal@nxp.com \
--cc=stable@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).