396c445cb1
We will use this in a future patch to determine whether it's safe to use DPDK allocated memory when allocating new 1gb page entries. We could use it in this patch to decide whether or not to register the memory hotplug handler, but there's really no harm registering it even when it's not needed. Ideally DPDK would provide some kind of API to query how DPDK was configured. In the normal case we know whether legacy-mem was specified, but if users initialize DPDK themselves and then call spdk_env_dpdk_post_init(), we won't know if legacy-mem was specified. So in that case, we will just assume that it wasn't specified. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ied0e5ff777c8ee651043f46a37ce62e44bfcc5fe Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/477086 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| env_internal.h | ||
| env.c | ||
| env.mk | ||
| init.c | ||
| Makefile | ||
| memory.c | ||
| pci_ioat.c | ||
| pci_nvme.c | ||
| pci_virtio.c | ||
| pci_vmd.c | ||
| pci.c | ||
| threads.c | ||