2015-06-23 20:59:57 -07:00
|
|
|
# -*- text -*-
|
2014-03-20 16:47:42 +00:00
|
|
|
#
|
|
|
|
|
# Copyright (c) 2014 Mellanox Technologies, Inc.
|
|
|
|
|
# All rights reserved.
|
|
|
|
|
# $COPYRIGHT$
|
2015-06-23 20:59:57 -07:00
|
|
|
#
|
2014-03-20 16:47:42 +00:00
|
|
|
# Additional copyrights may follow
|
2015-06-23 20:59:57 -07:00
|
|
|
#
|
2014-03-20 16:47:42 +00:00
|
|
|
# $HEADER$
|
|
|
|
|
#
|
|
|
|
|
#
|
|
|
|
|
|
2014-03-25 15:27:13 +00:00
|
|
|
[mmap:create segment failure]
|
2014-03-20 16:47:42 +00:00
|
|
|
|
2014-03-25 15:27:13 +00:00
|
|
|
You can try the following:
|
2014-03-20 18:22:12 +00:00
|
|
|
|
2014-03-25 15:27:13 +00:00
|
|
|
1. Decrease the symmetric heap area with
|
|
|
|
|
"-x SHMEM_SYMMETRIC_HEAP_SIZE=<value>".
|
|
|
|
|
2. Set "--mca sshmem_base_start_address 0" for
|
|
|
|
|
automatic selection by OS of virtual start address for sshmem.
|
2014-03-20 18:22:12 +00:00
|
|
|
|
2014-03-25 15:27:13 +00:00
|
|
|
This issue could also be related to CONFIG_STRICT_DEVMEM
|
|
|
|
|
kernel option which if enabled prevents access to physical
|
|
|
|
|
memory via "mmap". In this case you could try using other
|
|
|
|
|
sshmem components instead.
|
2014-11-05 16:38:28 +02:00
|
|
|
#
|
