[dpdk-dev] ivshmem mmap to specific address

Hi Eli > Is there a method to guarantee that this mapping won't fail, even for > different processes, that might have large code or constructors running even > before main? I'm afraid there is none. That's the nature of the beast. The best you can do is map stuff into a different address range

[dpdk-dev] ivshmem mmap to specific address

Hello, In librte_eal, in eal_ivshmem.c, in function map_all_segments, there is mapping of segments from the metadata to the same virtual address as written in the metadata. Is there a method to guarantee that this mapping won't fail, even for different processes, that might have large code