Repository navigation
hip: upload large tensors in windows so the blit can pin them - #2584
Conversation
|
@ElderOrb thanks for splitting this out. The windows stay inside the range |
eae27ed to
ee891d2
Compare
|
@ElderOrb, a small housekeeping change so this can land: the commit carried a personal email address as its author, and we keep those out of the public history. I re-authored it to your GitHub noreply address ( |
ee891d2 to
58b245e
Compare
|
Thank you @ElderOrb. This is merged into main with your commits under your own name, so you're listed as a TensorFold contributor. It ships in the next release, credited to you in the changelog and the release notes. |
|
Thanks @ElderOrb! This is in TensorFold 1.2.6, out now: https://github.com/ashhart/TensorFold/releases/tag/v1.2.6
|
A synchronous
hipMemcpyHtoDpins the host source for the lifetime of the blit. A single multi-gigabyte source fails to pin, so a large checkpoint cannot be uploaded at all. Copy in 64 MiB windows instead: the pin stays bounded, and a copy no larger than a window still takes one call.Split out of #2490 at review request: this is the one change there that is not ModelOpt-specific.
Ran: HIP on Windows, gfx1151, a 27B ModelOpt checkpoint (a single 20+ GiB upload) loads and serves.
Not run: any Linux HIP target, any other gfx target.