c833f6aa3e
The only release to not unlink hugepages after mmaping them is for multiprocess. But if shm_id is not specified, then we aren't using multiprocess. This ensures that all hugepages get released when the process exits, even if there is memory in those hugepages that was not freed during process shutdown. Make sure we don't enable both huge-unlink and single-file-segments at the same time though, DPDK doesn't support that. Note that even when using multi-process, if hugepages aren't released, they aren't really leaked. DPDK will clean them up next time the application runs. Fixes issue #2267. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I017bd4f7ed9cf6aaa141879539b099fb48f357f4 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10991 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| env_internal.h | ||
| env.c | ||
| env.mk | ||
| init.c | ||
| Makefile | ||
| memory.c | ||
| pci_event.c | ||
| pci_idxd.c | ||
| pci_ioat.c | ||
| pci_virtio.c | ||
| pci_vmd.c | ||
| pci.c | ||
| sigbus_handler.c | ||
| spdk_env_dpdk.map | ||
| threads.c | ||