Skip to content

Update Cuda provider config API #921

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

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

vinser52
Copy link
Contributor

@vinser52 vinser52 commented Nov 20, 2024

Description

Change the Cuda provider config as we agreed in #844

Checklist

  • Code compiles without errors locally
  • All tests pass locally
  • CI workflows execute properly
  • New tests added, especially if they will fail without my changes
  • Added/extended example(s) to cover this functionality

@vinser52 vinser52 requested a review from a team as a code owner November 20, 2024 12:45
@vinser52 vinser52 force-pushed the svinogra_cuda_params branch 3 times, most recently from 4b554ef to 0199253 Compare November 20, 2024 23:28
umf_cuda_memory_provider_params_handle_t cu_params = NULL;
umf_result_t umf_result = umfCudaMemoryProviderParamsCreate(&cu_params);
if (umf_result != UMF_RESULT_SUCCESS) {
fprintf(stderr, "Failed to create level zero params!\n");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[...] CUDA memory provider params!, same with the rest of the error messages in the consumer and producer.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@vinser52 vinser52 force-pushed the svinogra_cuda_params branch 2 times, most recently from bc080fa to c9c0cc2 Compare November 21, 2024 14:37
@bratpiorka
Copy link
Contributor

general note: when referring to a specific UMF pool provider/implementation, we should always use capital letters, e.g. we should write ‘UMF CUDA Memory Provider is an example of a memory provider implemented in UMF’ etc. We should also never write ‘Cuda’. Always use ‘CUDA’ in comments, and ‘cuda’ only as part of C variables/names, such as ‘umf_cuda_params’ etc.

/// @brief Create a struct to store parameters of the Cuda memory provider.
/// @param hParams [out] handle to the newly created parameters struct.
/// @return UMF_RESULT_SUCCESS on success or appropriate error code on failure.
umf_result_t umfCudaMemoryProviderParamsCreate(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please always write "CUDA" using capital letters as this is an acronym

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@vinser52 vinser52 force-pushed the svinogra_cuda_params branch from c9c0cc2 to d3a1398 Compare November 22, 2024 10:10
@lukaszstolarczuk lukaszstolarczuk merged commit 3d0fe19 into oneapi-src:main Nov 22, 2024
77 checks passed
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.

4 participants