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

Make reservation policy owning #250

Merged

Conversation

chillenzer
Copy link
Contributor

@chillenzer chillenzer commented Mar 27, 2024

Closes #244.

As discussed in #244, this makes the ReservePoolPolicies own the pool memory. We discussed that this might go beyond the scope of a "policy" but a renaming would break backwards compatibility, so should be well thought through. Tracked in #251.

@chillenzer chillenzer changed the title Topic make reservation policy owning Make reservation policy owning Mar 27, 2024
@psychocoderHPC psychocoderHPC marked this pull request as ready for review August 23, 2024 12:48
@psychocoderHPC psychocoderHPC added this to the 2.6.0crp milestone Aug 23, 2024
@chillenzer chillenzer force-pushed the topic-makeReservationPolicyOwning branch from 2f4a904 to 64d0aae Compare August 23, 2024 13:02
@chillenzer chillenzer force-pushed the topic-makeReservationPolicyOwning branch from 64d0aae to 929b695 Compare August 23, 2024 13:03
@psychocoderHPC psychocoderHPC merged commit b8a7c58 into alpaka-group:dev Aug 23, 2024
1 check 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.

Discrepancy between calls to setMemPool and resetMemPool
2 participants