From: Vamsi Attunuru <vattunuru@marvell.com>
To: <dev@dpdk.org>
Cc: Vamsi Attunuru <vattunuru@marvell.com>
Subject: [dpdk-dev] [PATCH v1 1/1] app/test: fix --socket-mem option in eal flag autotest
Date: Wed, 10 Apr 2019 12:55:32 +0530 [thread overview]
Message-ID: <20190410072532.17182-1-vattunuru@marvell.com> (raw)
"argv2[]" positive test case fails with RTE_MAX_NUMA_NODES=1 config
because of "--socket-mem=0,0,0,0" option, which passes memory sizes
for multiple sockets. This patch fixes the issue by passing memory
size for node 0 alone.
Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
---
app/test/test_eal_flags.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
index 9112c96..90df7b3 100644
--- a/app/test/test_eal_flags.c
+++ b/app/test/test_eal_flags.c
@@ -1161,7 +1161,7 @@ test_memory_flags(void)
/* valid (zero) --socket-mem flag */
const char *argv2[] = {prgname, "-c", "10", "-n", "2",
- "--file-prefix=" memtest, "--socket-mem=0,0,0,0"};
+ "--file-prefix=" memtest, "--socket-mem=0"};
/* invalid (incomplete) --socket-mem flag */
const char *argv3[] = {prgname, "-c", "10", "-n", "2",
--
2.8.4
next reply other threads:[~2019-04-10 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 7:25 Vamsi Attunuru [this message]
2019-04-10 7:25 ` Vamsi Attunuru
2019-04-10 8:26 ` David Marchand
2019-04-10 8:26 ` David Marchand
2019-04-10 11:43 ` [dpdk-dev] [EXT] " Vamsi Krishna Attunuru
2019-04-10 11:43 ` Vamsi Krishna Attunuru
2019-07-11 5:15 ` [dpdk-dev] [PATCH v2 " vattunuru
2019-07-11 13:56 ` Aaron Conole
2019-07-12 6:43 ` [dpdk-dev] [PATCH v3 " vattunuru
2019-07-23 6:13 ` Vamsi Krishna Attunuru
2019-07-26 13:39 ` David Marchand
2019-07-28 4:19 ` [dpdk-dev] [EXT] " Vamsi Krishna Attunuru
2019-07-29 8:08 ` [dpdk-dev] [PATCH v4] test: " David Marchand
2019-07-30 9:24 ` 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=20190410072532.17182-1-vattunuru@marvell.com \
--to=vattunuru@marvell.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).