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

Add in new HostAlloc API #9170

Merged
merged 3 commits into from
Sep 6, 2023
Merged

Conversation

revans2
Copy link
Collaborator

@revans2 revans2 commented Sep 1, 2023

This fixes #8879

The dependency for this was merged into CUDF today, but it may be a little while before this can be merged/tested.

Signed-off-by: Robert (Bobby) Evans <[email protected]>
@revans2 revans2 self-assigned this Sep 1, 2023
Copy link
Collaborator

@abellina abellina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've done one pass through the API. Overall it's looking good, I mostly had high level questions. Will wait for feedback and move onto tests sometime today.


import org.apache.spark.TaskContext

private class HostAlloc(nonPinnedLimit: Long) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, should we used "pageable" instead of "non-pinned"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you really want me to I will. Is it unclear the type of memory being allocated?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a nit, not a must fix. It is clear to me that non-pinned is pageable.


import org.apache.spark.TaskContext

private class HostAlloc(nonPinnedLimit: Long) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest we call this HostAllocator.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you really want me to I will. Is it unclear what this does?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the main nit I had was that HostAlloc sounded more like a product of an allocator than the allocator itself, but it's just a nit. Not a must fix.

@revans2 revans2 marked this pull request as ready for review September 5, 2023 20:15
@revans2
Copy link
Collaborator Author

revans2 commented Sep 5, 2023

build

@revans2
Copy link
Collaborator Author

revans2 commented Sep 5, 2023

build

@sameerz sameerz added the reliability Features to improve reliability or bugs that severly impact the reliability of the plugin label Sep 6, 2023
@revans2 revans2 merged commit 83ad213 into NVIDIA:branch-23.10 Sep 6, 2023
27 checks passed
@revans2 revans2 deleted the memory_limit_api branch September 6, 2023 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reliability Features to improve reliability or bugs that severly impact the reliability of the plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEA] Add host memory allocation APIs
4 participants