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 <dariuszx.stojaczyk@intel.com>
Reviewed-on: https://review.gerrithub.io/403594
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
Dariusz Stojaczyk 2018-03-13 00:05:02 +01:00 committed by Jim Harris
parent c45669cf89
commit 07526d85ef

View File

@ -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;
}