Hello
This seems to be the code for sharing the hwloc topology in shared
memory. This whole thing was designed for very large virtual spaces
(>=48bits on most CPUs) where it's easy to find a virtual memory area
that is unused in all participating processes. I am not sure it's worth
fixing on
Hello Ben
It will be back, at least for the majority of platforms (those without
heterogeneous memory).
See https://github.com/open-mpi/ompi/issues/8170 and
https://github.com/openpmix/prrte/pull/1141
Brice
Le 11/11/2021 à 05:33, Ben Menadue via devel a écrit :
Hi,
Quick question:
ary detect that the shmem
>>> region has already been mapped? If we attempt to map it and fail, does that
>>> mean it has already been mapped or that it doesn't exist?
>>>
>>> It isn't reasonable to expect that all the libraries in a process will
>>> coord
Hello Ralph
One thing that isn't clear in this document : the hwloc shmem region may
only be mapped *once* per process (because the mmap address is always
the same). Hence, if a library calls adopt() in the process, others will
fail. This applies to the 2nd and 3rd case in "Accessing the HWLOC
FYI, this was a git bug that will be fixed soon (the range of commits
being rebased was wrong).
https://lore.kernel.org/git/pull.789.git.1605314085.gitgitgad...@gmail.com/T/#t
https://lore.kernel.org/git/20d6104d-ca02-4ce4-a1c0-2f9386ded...@gmail.com/T/#t
Brice
Le 07/02/2020 à 10:27, Brice
Hello
I have a git submodule issue that I don't understand.
PR#7367 was initially on top of PR #7366. When Jeff merged PR#7366, I
rebased my #7367 with git prrs and got this error:
$ git prrs origin master
>From https://github.com/open-mpi/ompi
* branch master ->
Thanks a lot for writing all this.
At the end
https://github.com/open-mpi/ompi/wiki/GitSubmodules#adding-a-new-submodule-pointing-to-a-specific-commit
should "bar" be "bar50x" in line "$ git add bar" ?
It seems to me that you are in opal/mca/foo and the new submodule is in
"bar50x" (according
