| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
mlock alone is page-locked for AIO but not device-pinned; cudaHostRegister after alloc restores torch-class H2D/D2H bandwidth. Signed-off-by: Olatunji Ruwase <tunji.ruwase@snowflake.com> Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Here are some automated review suggestions for this pull request.
Reviewed commit: e6bea83b5d
ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Sorry, something went wrong.
cudaHostUnregister must succeed before returning the allocation, or the driver can keep a registration on recycled host pages. Signed-off-by: Olatunji Ruwase <tunji.ruwase@snowflake.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi @sfc-gh-truwase I'm generally okay with this PR. The only thing I want to add is XPU implementation of register_host_memory, which should be added from a seperate PR. I'll approve your PR. |
Sorry, something went wrong.
@delock, good call. Please let me know when this is done. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
H200 H2D/D2H (1 GPU)
Host tunji-h200-n1g2-ds-pin-0, NVIDIA H200, --sizes-mib 4 64 256 --warmup 10 --iters 50, autorun job-20260820T155549Z.
Registered native matches torch bandwidth (~53–55 GB/s). mlock without cudaHostRegister stays in the ~10–17 GB/s pageable range and reports torch.is_pinned=False.
Test plan
Made with Cursor