Skip to content

v2.x reduce vader XPMEM memory footprint #2382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 8, 2016
Merged

Conversation

hjelmn
Copy link
Member

@hjelmn hjelmn commented Nov 7, 2016

No description provided.

shamisp and others added 2 commits November 7, 2016 15:58
The original VADER_MAX_ADDRESS was tunned for x86_64 platforms only.
For non x86_64 platforms we can use XPMEM_MAXADDR_SIZE.

Signed-off-by: Pavel Shamis (Pasha) <[email protected]>
(cherry picked from commit 60fd25f)
Signed-off-by: Nathan Hjelm <[email protected]>
The vader btl kept a per-peer registration cache to keep track of
attachments. This is not really a problem with small numbers of local
ranks but can be a problem with large SMP machines. To reduce the
footprint there is now one registration cache for all xpmem
attachments. This will probably increase the lookup time for large
transfers but is a worthwhile trade-off.

Signed-off-by: Nathan Hjelm <[email protected]>
(cherry picked from commit a652a19)
Signed-off-by: Nathan Hjelm <[email protected]>
@hjelmn hjelmn added the bug label Nov 7, 2016
@hjelmn hjelmn added this to the v2.1.0 milestone Nov 7, 2016
@jsquyres jsquyres merged commit a754501 into open-mpi:v2.x Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants