I was able to trace down this issue to a particular function call I was making on a closed-source library that scans the PCIe bus. I don't know why it was causing it, since I can't see what it's doing. However, if I remove that function call, the warnings go away completely. If I add it back, it comes back reliably. For anyone else reading this, try moving your rte_eal_init earlier in your startup to see if there's a particular function causing it.
On Thu, Nov 15, 2018 at 12:33 PM Cliff Burdick <[email protected]> wrote: > Not sure how that is happening. 1GB hugepages are enabled on boot, and > that's the only one allocated: > > $ ls /sys/kernel/mm/hugepages/ > hugepages-1048576kB > > $ mount > ... > nodev on /mnt/huge type hugetlbfs (rw,relatime,pagesize=1024M) > > Any idea where the 4K alignment is coming from? > > On Thu, Nov 15, 2018 at 11:54 AM Kyle Larose <[email protected]> wrote: > >> On Thu, Nov 15, 2018 at 2:30 PM Cliff Burdick <[email protected]> wrote: >> > >> > Hi, I'm updating to 18.11 from 17.03, and I noticed there a several new >> > warnings printing on startup in my primary process: >> > >> ... >> > EAL: WARNING! Base virtual address hint (0x64002f000 != 0x680000000) not >> > respected! >> > EAL: This may cause issues with mapping memory into secondary >> processes >> > EAL: WARNING! Base virtual address hint (0xe80030000 != 0xec0000000) not >> > respected! >> > EAL: This may cause issues with mapping memory into secondary >> processes >> > EAL: WARNING! Base virtual address hint (0x16c0031000 != 0x1700000000) >> not >> > respected! >> ... >> > >> > It appears by searching the mailing list that this problem is not very >> > common since it's fairly new. Does anyone know what can cause this? I >> have >> > ASLR disabled. >> >> 4K pages vs huge-pages? It looks like the left-hand addresses are >> 4K-aligned, while the right-hand ones are not. >> >
