Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

src/cunumeric/search: make nonzero not always allocate SYS_MEM buffers #572

Merged
merged 2 commits into from
Sep 2, 2022
Merged

src/cunumeric/search: make nonzero not always allocate SYS_MEM buffers #572

merged 2 commits into from
Sep 2, 2022

Commits on Sep 2, 2022

  1. src/cunumeric/search: make nonzero not always allocate SYS_MEM buffers 

    This commit fixes a bug where nonzero would always allocate data in
system memory for output buffers even when numa memories were available.
This led to error messages like:
```
[0 - 7f2e7001d000]    1.243573 {5}{runtime}: [error 608] LEGION ERROR: Field 1048586 of output region 0 of task cunumeric::NonzeroTask (UID: 58) is requested to have an instance on memory 1e00000000000002, but the returned instance is allocated on memory 1e00000000000000. (from file /opt/legate/legate.core/legion/runtime/legion/runtime.cc:5797)
For more information see:
http://legion.stanford.edu/messages/error_code.html#error_code_608
```
    @rohany
    rohany committed Sep 2, 2022
    Configuration menu
    Copy the full SHA
    473de86 View commit details
    Browse the repository at this point in the history

  2. src/cunumeric/set: make unique not always allocate in SYS_MEM 

    This commit fixes a bug where `unique` would always allocate buffers in
system memory, even when numa memory is available.
    @rohany
    rohany committed Sep 2, 2022
    Configuration menu
    Copy the full SHA
    aa32d90 View commit details
    Browse the repository at this point in the history