[dpdk-stable] [PATCH] test/flow-classify: fix failure on dual socket systems

[Harry van Haaren]

This commit fixes failures of the flow_classify_autotest when
ran on dual-socket servers, as the sample application does not
support more than a single socket. Increasing the NB_SOCKETS
value allows the test to run successfully.

Fixes: 9c9befea4f57 ("test: add flow classify unit tests")

Signed-off-by: Harry van Haaren <harry.van.haaren at intel.com>

---

DPDK does not provide a RTE_SOCKETS_MAX #define, so we cannot
easily statically allocate the array. As a bugfix patch, I'd
prefer not add complexity of dynamically allocating based on
rte_socket_count(), hence just increasing the value seems the
most pragmatic fix.

Fixes: tag is a bit complex, code was moved in previous commit.
This fixes tag is against when the NB_SOCKET = 1 was introduced.

Cc: stable at dpdk.org

---
 app/test/test_flow_classify.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/test/test_flow_classify.c b/app/test/test_flow_classify.c
index ff5265c6a..ef0b6fdd5 100644
--- a/app/test/test_flow_classify.c
+++ b/app/test/test_flow_classify.c
@@ -23,7 +23,7 @@
 
 #define FLOW_CLASSIFY_MAX_RULE_NUM 100
 #define MAX_PKT_BURST              32
-#define NB_SOCKETS                 1
+#define NB_SOCKETS                 4
 #define MEMPOOL_CACHE_SIZE         256
 #define MBUF_SIZE                  512
 #define NB_MBUF                    512
-- 
2.17.1