test: check zero socket memory as valid
authorIlya Maximets <i.maximets@samsung.com>
Fri, 25 Jan 2019 07:55:58 +0000 (10:55 +0300)
committerThomas Monjalon <thomas@monjalon.net>
Sat, 26 Jan 2019 18:24:04 +0000 (19:24 +0100)
Dynamic memory mode allowes zero socket-mem because all the
required memory could be allocated on demand.

Fixes: 0a703f0f36c1 ("eal/linux: fix parsing zero socket memory and limits")
Cc: stable@dpdk.org
Reported-by: Shuai Zhu <shuaix.zhu@intel.com>
Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
test/test/test_eal_flags.c

index e3a60c7..81e345b 100644 (file)
@@ -1158,7 +1158,7 @@ test_memory_flags(void)
        const char *argv1[] = {prgname, "-c", "10", "-n", "2",
                        "--file-prefix=" memtest, "-m", DEFAULT_MEM_SIZE};
 
-       /* invalid (zero) --socket-mem flag */
+       /* valid (zero) --socket-mem flag */
        const char *argv2[] = {prgname, "-c", "10", "-n", "2",
                        "--file-prefix=" memtest, "--socket-mem=0,0,0,0"};
 
@@ -1256,8 +1256,8 @@ test_memory_flags(void)
                printf("Error - process failed with valid -m flag!\n");
                return -1;
        }
-       if (launch_proc(argv2) == 0) {
-               printf("Error - process run ok with invalid (zero) --socket-mem!\n");
+       if (launch_proc(argv2) != 0) {
+               printf("Error - process failed with valid (zero) --socket-mem!\n");
                return -1;
        }