Use region_t's for mapped memory #594
Assignees
Labels
Comments
eyalroz
added a commit
that referenced
this issue
Feb 29, 2024
* `memory::mapped::region_pair_t` now has two `memory::region_t` members * Can easily imbue the mapped region with a type - by viewing it as a pair of spans; have a special struct for that, which also implicitly converts into an `std::pair` of spans * Amended the vectorAddMapped example to make use of these new facilities * Can now `get_device_region_for()` in addition to `get_device_pointer_for` - for the host-side of mapped regions
eyalroz
added a commit
that referenced
this issue
Mar 1, 2024
* `memory::mapped::region_pair_t` now has two `memory::region_t` members * Can easily imbue the mapped region with a type - by viewing it as a pair of spans; have a special struct for that, which also implicitly converts into an `std::pair` of spans * Amended the vectorAddMapped example to make use of these new facilities * Can now `get_device_region_for()` in addition to `get_device_pointer_for` - for the host-side of mapped regions
eyalroz
added a commit
that referenced
this issue
Apr 20, 2024
* `memory::mapped::region_pair_t` now has two `memory::region_t` members * Can easily imbue the mapped region with a type - by viewing it as a pair of spans; have a special struct for that, which also implicitly converts into an `std::pair` of spans * Amended the vectorAddMapped example to make use of these new facilities * Can now `get_device_region_for()` in addition to `get_device_pointer_for` - for the host-side of mapped regions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
cuda::memory::mapped::region_pairstructure uses two raw pointers and a size field. Instead, let's make it a pair ofmemory::region_t's. Yes, it is a bit "wasteful" - another size_t value; but much more usable, and the pair might be optimized away, anyway.The text was updated successfully, but these errors were encountered: