From: Cliff Burdick <shaklee3@gmail.com>
To: eomereadig@gmail.com
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] WARNING! Base virtual address hint not respected!
Date: Thu, 15 Nov 2018 12:33:53 -0800 [thread overview]
Message-ID: <CA+Gp1nbyDwLskT7eer5ZFCNc_UDgh=zodHrP09snyczPzEee0w@mail.gmail.com> (raw)
In-Reply-To: <CAMFWN9n4zpqsd+rQ2SuAtLea3PvHNmx5BXwHEgf8o+ZX=N36xw@mail.gmail.com>
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.
>
next prev parent reply other threads:[~2018-11-15 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 19:30 Cliff Burdick
2018-11-15 19:54 ` Kyle Larose
2018-11-15 20:33 ` Cliff Burdick [this message]
2018-11-17 3:51 ` Cliff Burdick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+Gp1nbyDwLskT7eer5ZFCNc_UDgh=zodHrP09snyczPzEee0w@mail.gmail.com' \
--to=shaklee3@gmail.com \
--cc=eomereadig@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).