Skip to content

[XLA:GPU] Port VMM allocator allocations to records#44224

Draft
shawnwang18 wants to merge 1 commit into
openxla:pr4_vmm_allocator_record_modelfrom
shawnwang18:pr4_vmm_allocator_record_allocations
Draft

[XLA:GPU] Port VMM allocator allocations to records#44224
shawnwang18 wants to merge 1 commit into
openxla:pr4_vmm_allocator_record_modelfrom
shawnwang18:pr4_vmm_allocator_record_allocations

Conversation

@shawnwang18

Copy link
Copy Markdown
Contributor

📝 Summary of Changes
Ports allocator-address ownership in DeviceAddressVmmAllocator to AllocationRecord. Allocate(), mapped Allocate(), Deallocate(), pending allocator deallocation, reuse, and allocator-address getters now use record-backed state. Reservation aliases remain on the existing ReservationMapping maps for the next slice.

🎯 Justification
This isolates the allocator-address state migration from the reservation-alias migration, keeping each review focused and preserving the existing external behavior.

🚀 Kind of Contribution
♻️ Cleanup

📊 Benchmark (for Performance Improvements)
N/A.

🧪 Unit Tests:
Not run locally. Intended validation: bazel build //xla/stream_executor:device_address_vmm_allocator //xla/stream_executor/cuda:cuda_device_address_vmm_allocator and bazel test //xla/stream_executor/cuda:cuda_device_address_vmm_allocator_test.

🧪 Execution Tests:
Not run locally.

@shawnwang18 shawnwang18 force-pushed the pr4_vmm_allocator_record_model branch from fdf77c2 to 5e00368 Compare June 12, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant