Rework the range_attribute_t and advice code #640
Labels
Comments
eyalroz
changed the title
memory::region_t class
eyalroz
added a commit
that referenced
this issue
Apr 20, 2024
* The user no longer sees `range_attribute_t` nor `advice_t` anywhere, they're within `detail_` * Using a range namespace (although it's mostly for the `detail_` subnamespace), with `advice_t` and `attribute_t` types * Now have a proper implementation of a setter for device-inspecific attributes * Removed some redundant code
eyalroz
added a commit
that referenced
this issue
Apr 29, 2024
* The user no longer sees `range_attribute_t` nor `advice_t` anywhere, they're within `detail_` * Using a range namespace (although it's mostly for the `detail_` subnamespace), with `advice_t` and `attribute_t` types * Now have a proper implementation of a setter for device-inspecific attributes * Removed some redundant code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Managed memory "ranges" have "attributes" in CUDA. But our class name for "ranges" of memory - managed or otherwise - is
memory::managed::region_t. Also - it's not obvious we should even expose these "attribute" and "advice" types, at all; perhaps we can just keep them withindetail_. Some refactoring seems to be in order.The text was updated successfully, but these errors were encountered: