DPDK-dev Archive on lore.kernel.org
 help / color / Atom feed
* [dpdk-dev] warning on remapping memory
       [not found] <320C85BA-8752-4BE6-B5DB-5886D257F5AC@nvidia.com>
@ 2019-06-11 18:50 ` Yongseok Koh
  2019-06-12 12:57   ` Burakov, Anatoly
  0 siblings, 1 reply; 2+ messages in thread
From: Yongseok Koh @ 2019-06-11 18:50 UTC (permalink / raw)
  To: Burakov, Anatoly; +Cc: dev, Elena Agostini, Wojtek Wasko

Hi Anatoly,

There's a report that remap fails on a specific x86 host.
We can silence this warning by specifying '--base-virtaddr',
but wondering if you know in which case it could happen.

Log attached.


Thanks,
Yongseok
 
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 8 on socket 0
EAL: Detected lcore 7 as core 9 on socket 0
EAL: Detected lcore 8 as core 10 on socket 0
EAL: Detected lcore 9 as core 11 on socket 0
EAL: Detected lcore 10 as core 12 on socket 0
EAL: Detected lcore 11 as core 13 on socket 0
EAL: Detected lcore 12 as core 16 on socket 0
EAL: Detected lcore 13 as core 17 on socket 0
EAL: Detected lcore 14 as core 18 on socket 0
EAL: Detected lcore 15 as core 19 on socket 0
EAL: Detected lcore 16 as core 20 on socket 0
EAL: Detected lcore 17 as core 21 on socket 0
EAL: Detected lcore 18 as core 24 on socket 0
EAL: Detected lcore 19 as core 25 on socket 0
EAL: Detected lcore 20 as core 26 on socket 0
EAL: Detected lcore 21 as core 27 on socket 0
EAL: Detected lcore 22 as core 28 on socket 0
EAL: Detected lcore 23 as core 29 on socket 0
EAL: Detected lcore 24 as core 0 on socket 1
EAL: Detected lcore 25 as core 1 on socket 1
EAL: Detected lcore 26 as core 2 on socket 1
EAL: Detected lcore 27 as core 3 on socket 1
EAL: Detected lcore 28 as core 4 on socket 1
EAL: Detected lcore 29 as core 5 on socket 1
EAL: Detected lcore 30 as core 8 on socket 1
EAL: Detected lcore 31 as core 9 on socket 1
EAL: Detected lcore 32 as core 10 on socket 1
EAL: Detected lcore 33 as core 11 on socket 1
EAL: Detected lcore 34 as core 12 on socket 1
EAL: Detected lcore 35 as core 13 on socket 1
EAL: Detected lcore 36 as core 16 on socket 1
EAL: Detected lcore 37 as core 17 on socket 1
EAL: Detected lcore 38 as core 18 on socket 1
EAL: Detected lcore 39 as core 19 on socket 1
EAL: Detected lcore 40 as core 20 on socket 1
EAL: Detected lcore 41 as core 21 on socket 1
EAL: Detected lcore 42 as core 24 on socket 1
EAL: Detected lcore 43 as core 25 on socket 1
EAL: Detected lcore 44 as core 26 on socket 1
EAL: Detected lcore 45 as core 27 on socket 1
EAL: Detected lcore 46 as core 28 on socket 1
EAL: Detected lcore 47 as core 29 on socket 1
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 48 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or directory)
EAL: VFIO PCI modules not loaded
EAL: DPAA Bus not present. Skipping.
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: page_sz=4096, elt_sz=72, len=2560, mmap_len=188416
EAL: Ask a virtual area of 0x2e000 bytes
EAL: Virtual area found at 0x100000000 (size = 0x2e000)
EAL: Setting up physically contiguous memory...
EAL: Setting maximum number of open files to 1048576
EAL: Detected memory type: socket_id:0 hugepage_sz:1073741824
EAL: Detected memory type: socket_id:1 hugepage_sz:1073741824
EAL: Creating 4 segment lists: n_segs:32 socket_id:0 hugepage_sz:1073741824
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: Virtual area found at 0x10002e000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 0
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x24002f000 != 0x7f9bc0000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f9bc0000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0x280034000 != 0x7fa4294b1000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294b1000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 0
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x3c0035000 != 0x7f9380000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f9380000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0x40003a000 != 0x7fa4294b0000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294b0000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 0
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x54003b000 != 0x7f8b40000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f8b40000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0x580040000 != 0x7fa4294af000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294af000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 0
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x640041000 != 0x680000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x680000000 (size = 0x800000000)
EAL: Creating 4 segment lists: n_segs:32 socket_id:1 hugepage_sz:1073741824
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: Virtual area found at 0x640041000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 1
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x780042000 != 0x7f8300000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f8300000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0x7c0047000 != 0x7fa4294ae000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294ae000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 1
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0x900048000 != 0x7f7ac0000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f7ac0000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0x94004d000 != 0x7fa4294ad000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294ad000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 1
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0xa8004e000 != 0x7f7280000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f7280000000 (size = 0x800000000)
EAL: page_sz=4096, elt_sz=48, len=32, mmap_len=4096
EAL: Ask a virtual area of 0x1000 bytes
EAL: WARNING! Base virtual address hint (0xac0053000 != 0x7fa4294ac000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7fa4294ac000 (size = 0x1000)
EAL: Memseg list allocated: 0x100000kB at socket 1
EAL: Ask a virtual area of 0x800000000 bytes
EAL: WARNING! Base virtual address hint (0xc00054000 != 0x7f6a40000000) not respected!
EAL:    This may cause issues with mapping memory into secondary processes
EAL: Virtual area found at 0x7f6a40000000 (size = 0x800000000)
EAL: TSC frequency is ~2700000 KHz
EAL: Master lcore 0 is ready (tid=7fa4294a1000;cpuset=[0])
EAL: lcore 7 is ready (tid=7fa41b4c7700;cpuset=[7])
EAL: lcore 8 is ready (tid=7fa41acc6700;cpuset=[8])
EAL: lcore 9 is ready (tid=7fa41a4c5700;cpuset=[9])
EAL: lcore 6 is ready (tid=7fa41bcc8700;cpuset=[6])
EAL: lcore 2 is ready (tid=7fa41dccc700;cpuset=[2])
EAL: lcore 1 is ready (tid=7fa41e4cd700;cpuset=[1])
EAL: lcore 4 is ready (tid=7fa41ccca700;cpuset=[4])
EAL: lcore 3 is ready (tid=7fa41d4cb700;cpuset=[3])
EAL: lcore 5 is ready (tid=7fa41c4c9700;cpuset=[5])
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 1024MB
EAL: PCI device 0000:3f:00.0 on NUMA socket 0
EAL:   probe driver: 15b3:1017 net_mlx5
EAL: Mem event callback 'MLX5_MEM_EVENT_CB:(nil)' registered
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


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

* Re: [dpdk-dev] warning on remapping memory
  2019-06-11 18:50 ` [dpdk-dev] warning on remapping memory Yongseok Koh
@ 2019-06-12 12:57   ` Burakov, Anatoly
  0 siblings, 0 replies; 2+ messages in thread
From: Burakov, Anatoly @ 2019-06-12 12:57 UTC (permalink / raw)
  To: Yongseok Koh; +Cc: dev, Elena Agostini, Wojtek Wasko

On 11-Jun-19 7:50 PM, Yongseok Koh wrote:
> Hi Anatoly,
> 
> There's a report that remap fails on a specific x86 host.
> We can silence this warning by specifying '--base-virtaddr',
> but wondering if you know in which case it could happen.
> 
> Log attached.
> 
> 
> Thanks,
> Yongseok
>   

What DPDK version is this?

In any case, i don't think there are specific circumstances in which 
this is likely or unlikely to happen. Anything could be occupying those 
addresses - libraries, code, more libraries, more code... The address is 
taken, and EAL reports it. If you're not going to use secondary 
processes, it can be ignored. If you are, well, truth is there's little 
you can do to fix it :( This is just a byproduct of how our secondary 
processes work.

-- 
Thanks,
Anatoly

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

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <320C85BA-8752-4BE6-B5DB-5886D257F5AC@nvidia.com>
2019-06-11 18:50 ` [dpdk-dev] warning on remapping memory Yongseok Koh
2019-06-12 12:57   ` Burakov, Anatoly

DPDK-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/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 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \
		dev@dpdk.org dpdk-dev@archiver.kernel.org
	public-inbox-index dpdk-dev


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.dpdk.dev


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