DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] WARNING! Base virtual address hint not respected!
@ 2018-11-15 19:30 Cliff Burdick
  2018-11-15 19:54 ` Kyle Larose
  0 siblings, 1 reply; 4+ messages in thread
From: Cliff Burdick @ 2018-11-15 19:30 UTC (permalink / raw)
  To: users

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: Detected 48 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
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!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x1f00032000 != 0x1f40000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x2740033000 != 0x2780000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x2f80034000 != 0x2fc0000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x37c0035000 != 0x3800000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x4000036000 != 0x4040000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-users] WARNING! Base virtual address hint not respected!
  2018-11-15 19:30 [dpdk-users] WARNING! Base virtual address hint not respected! Cliff Burdick
@ 2018-11-15 19:54 ` Kyle Larose
  2018-11-15 20:33   ` Cliff Burdick
  0 siblings, 1 reply; 4+ messages in thread
From: Kyle Larose @ 2018-11-15 19:54 UTC (permalink / raw)
  To: shaklee3; +Cc: users

On Thu, Nov 15, 2018 at 2:30 PM Cliff Burdick <shaklee3@gmail.com> 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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-users] WARNING! Base virtual address hint not respected!
  2018-11-15 19:54 ` Kyle Larose
@ 2018-11-15 20:33   ` Cliff Burdick
  2018-11-17  3:51     ` Cliff Burdick
  0 siblings, 1 reply; 4+ messages in thread
From: Cliff Burdick @ 2018-11-15 20:33 UTC (permalink / raw)
  To: eomereadig; +Cc: users

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 <eomereadig@gmail.com> wrote:

> On Thu, Nov 15, 2018 at 2:30 PM Cliff Burdick <shaklee3@gmail.com> 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.
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-users] WARNING! Base virtual address hint not respected!
  2018-11-15 20:33   ` Cliff Burdick
@ 2018-11-17  3:51     ` Cliff Burdick
  0 siblings, 0 replies; 4+ messages in thread
From: Cliff Burdick @ 2018-11-17  3:51 UTC (permalink / raw)
  To: Kyle Larose; +Cc: users

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 <shaklee3@gmail.com> 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 <eomereadig@gmail.com> wrote:
>
>> On Thu, Nov 15, 2018 at 2:30 PM Cliff Burdick <shaklee3@gmail.com> 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.
>>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-11-17  3:51 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-15 19:30 [dpdk-users] WARNING! Base virtual address hint not respected! Cliff Burdick
2018-11-15 19:54 ` Kyle Larose
2018-11-15 20:33   ` Cliff Burdick
2018-11-17  3:51     ` Cliff Burdick

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).