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

[FEA] Use cudf::io::config_host_memory_resource #10814

Closed
abellina opened this issue May 14, 2024 · 1 comment
Closed

[FEA] Use cudf::io::config_host_memory_resource #10814

abellina opened this issue May 14, 2024 · 1 comment
Assignees
Labels
task Work required that improves the product but is not user facing

Comments

@abellina
Copy link
Collaborator

Filing this as P0 to call the new config_host_memory_resource api in 24.06 so we can disable an extra pinned allocation that would happen otherwise.

We will want to revisit our pinned pool MR in 24.08+ to align closer to the whole-cuDF pinned pool.

@abellina abellina added feature request New feature or request ? - Needs Triage Need team to review and classify labels May 14, 2024
@abellina abellina self-assigned this May 14, 2024
@sameerz sameerz added task Work required that improves the product but is not user facing and removed feature request New feature or request ? - Needs Triage Need team to review and classify labels May 14, 2024
@abellina
Copy link
Collaborator Author

This is actually handled by #10868. We are calling the right APIs trying to disable the cuDF pinned pool early enough, and if we fail we end up with 100MB that cuDF uses and we won't (this should not happen). We warn if we fail, but we continue as we can go on with our pool, I don't think there's work left here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Work required that improves the product but is not user facing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants