DPDK usage discussions
 help / color / mirror / Atom feed
From: Gavan Newell <gavan.newell@redfignetworks.com.au>
To: users@dpdk.org
Subject: [dpdk-users] EAL: WARNING! Base virtual address hint not respected after upgrade from DPDK 18.11 to 20.11.1
Date: Thu, 8 Apr 2021 11:34:07 +1000
Message-ID: <CAMZHN5GzH+zQFA6GJ8EWWYq6uTM123Rh13wEW5HqH8FKN7Se9A@mail.gmail.com> (raw)

Hello,

I am in the process of upgrading my application from DPDK 18.11 to 20.11.1.
My particular application is slightly unusual in that I am calling DPDK
from Java using JNI. This has worked previously in 18.11.

When I run my application under 20.11.1 I get the output shown below before
it crashes with a coredump at my call to rte_eth_rx_burst(). I suspect that
the issue is related to the warning messages, as they don't appear if I run
the application directly (i.e. bypassing Java JNI).

EAL: Detected 24 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Static memory layout is selected, amount of reserved memory can be
adjusted with -m or --socket-mem
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: WARNING! Base virtual address hint (0x240036000 != 0x7f7c80000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x3c0037000 != 0x7f7440000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x540038000 != 0x7f6c00000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x6c0039000 != 0x7f63c0000000) not
respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: PCI device 0000:41:00.0 on NUMA socket 1
EAL:   probe driver: 8086:154d net_ixgbe
EAL: PCI device 0000:41:00.1 on NUMA socket 1
EAL:   probe driver: 8086:154d net_ixgbe
EAL: PCI device 0000:42:00.0 on NUMA socket 1
EAL:   probe driver: 8086:154d net_ixgbe
EAL: PCI device 0000:42:00.1 on NUMA socket 1
EAL:   probe driver: 8086:154d net_ixgbe

Is there some EAL argument I can provide to avoid this coredump?

Thanks!


Gavan

                 reply	other threads:[~2021-04-08  1:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMZHN5GzH+zQFA6GJ8EWWYq6uTM123Rh13wEW5HqH8FKN7Se9A@mail.gmail.com \
    --to=gavan.newell@redfignetworks.com.au \
    --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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git