[dpdk-dev] [PATCH v1 1/1] app/test: fix --socket-mem option in eal flag autotest

Vamsi Attunuru vattunuru at marvell.com
Wed Apr 10 09:25:32 CEST 2019


"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 at 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



More information about the dev mailing list