-
Notifications
You must be signed in to change notification settings - Fork 112
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.
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
Update verification check to save memory #128
Milestone
Comments
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 3, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 3, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 3, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
gonzalobg
added a commit
to gonzalobg/BabelStream
that referenced
this issue
Jun 4, 2024
This commit puts benchmarks in control of allocating the host memory used for verifying the results. This enables benchmarks that use Unified Memory for the device allocations, to avoid the host-side allocation and just pass pointers to the device allocation to the benchmark driver. Closes UoB-HPC#128 .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The OpenMP CPU version allocates twice the memory it needs restricting the maximum problem size.
For offload models, this is OK as the data needs to exists on the device during the run and on the host during verification.
This could be solved by asking the implementations to pass a pointer to host data back to the driver routine for checking, rather than copying into a vector allocated by the driver.
This would allow implementations to do save memory where possible.
The text was updated successfully, but these errors were encountered: