90bf3f89ed
Currently, EAL init in secondary processes will attach all fbarrays
in the memconfig to have access to the primary process's page tables.
However, fbarrays corresponding to external memory segments should
not be attached at initialization, because this will happen as part
of `rte_extmem_attach` [1] or `rte_malloc_heap_memory_attach` [2] calls.
1: https://doc.dpdk.org/api/rte__memory_8h.html#a2796da68de6825f8edf53759f8e4d230
2: https://doc.dpdk.org/api/rte__malloc_8h.html#af6360dea35bdf162feeb2b62cf149fd3
Fixes:
|
||
|---|---|---|
| .. | ||
| include | ||
| eal_alarm_private.h | ||
| eal_alarm.c | ||
| eal_cpuflags.c | ||
| eal_debug.c | ||
| eal_dev.c | ||
| eal_hugepage_info.c | ||
| eal_interrupts.c | ||
| eal_lcore.c | ||
| eal_memalloc.c | ||
| eal_memory.c | ||
| eal_thread.c | ||
| eal_timer.c | ||
| eal.c | ||
| meson.build | ||