Skip to content
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

smsc/accelerator: add new smsc component #12949

Merged
merged 2 commits into from
Dec 9, 2024

Conversation

edgargabriel
Copy link
Member

@edgargabriel edgargabriel commented Dec 2, 2024

  • add smsc component based on the accelerator API IPC functionality.
  • adjust smsc base selection logic to enable a pass-through mechanism with the new smsc/accelerator component

By default, the smsc/accelerator component is disabled to avoid a small hit on the latency for host memory.

The smsc/accelerator component forwards host memory to the 'next' smsc component. This mechanism has been tested with cma and xpmem, but not with knem (due to a lack of a system with knem installed).

@edgargabriel edgargabriel requested a review from bosilca December 2, 2024 19:18
@edgargabriel edgargabriel force-pushed the topic/smsc-accelerator branch 3 times, most recently from b7339f3 to 217cf28 Compare December 4, 2024 16:49
- add smsc component based on the accelerator API IPC functionality.
- adjust smsc base selection logic to enable a pass-through mechanism
  with the new smsc/accelerator component

Signed-off-by: Edgar Gabriel <[email protected]>
when using the blocking hipMemcpy version of the _memcpy
operation we seem to need a synchronization of the default stream to
ensure completeness in some cases.

Signed-off-by: Edgar Gabriel <[email protected]>
@edgargabriel edgargabriel force-pushed the topic/smsc-accelerator branch from 217cf28 to 4a117d5 Compare December 9, 2024 22:01
@edgargabriel edgargabriel merged commit ec987ee into open-mpi:main Dec 9, 2024
15 checks passed
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.

2 participants