From 07526d85ef7bf98ea2dacaaa8c1c1857b648b8ab Mon Sep 17 00:00:00 2001 From: Dariusz Stojaczyk Date: Tue, 13 Mar 2018 00:05:02 +0100 Subject: [PATCH] env/dpdk: use MEMPOOL_F_NO_PHYS_CONTIG This is required for DPDK's single file segments. Without this flag, mempools are likely to fail to create. We don't necesarrily depend on physical contiguity anywhere in SPDK and a quick NVMe+UIO perf test shows no performance regressions. Change-Id: I6b36b66bedfc99ee491663b5f2d21e079de12c44 Signed-off-by: Dariusz Stojaczyk Reviewed-on: https://review.gerrithub.io/403594 Tested-by: SPDK Automated Test System Reviewed-by: Daniel Verkamp Reviewed-by: Jim Harris --- lib/env_dpdk/env.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/env_dpdk/env.c b/lib/env_dpdk/env.c index 5dc12a8ba..d13210307 100644 --- a/lib/env_dpdk/env.c +++ b/lib/env_dpdk/env.c @@ -183,7 +183,7 @@ spdk_mempool_create_ctor(const char *name, size_t count, mp = rte_mempool_create(name, count, ele_size, cache_size, 0, NULL, NULL, (rte_mempool_obj_cb_t *)obj_init, obj_init_arg, - socket_id, 0); + socket_id, MEMPOOL_F_NO_PHYS_CONTIG); return (struct spdk_mempool *)mp; }