Skip to content

Return the global memory with enough capacity as default mem_id #361

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
Jul 22, 2024

Conversation

sophimao
Copy link
Contributor

@sophimao sophimao commented May 6, 2024

For heterogeneous memory system where each global memory has the same size, the memory with address range starting at 0x0 may have a smaller usable range than the other memories as we need to avoid allocating at 0x0. As a result, if user allocates a buffer with size of CL_DEVICE_MAX_MEM_ALLOC_SIZE, it will need to be allocated to one of the other memories. This change updates the way default gmem_id is found, by taking the allocation size into account.

@sophimao sophimao force-pushed the agilex_hetero_diag branch from bda6ec5 to 2c38a36 Compare May 6, 2024 16:47
@sophimao sophimao marked this pull request as ready for review May 6, 2024 16:55
@sophimao sophimao requested a review from rho180 May 7, 2024 13:14
@sophimao sophimao requested review from mendell27 and justin-rosner and removed request for rho180 June 10, 2024 14:09
@sophimao sophimao force-pushed the agilex_hetero_diag branch from 2c38a36 to 7e5800e Compare July 17, 2024 17:11
@sophimao sophimao merged commit 646453d into intel:main Jul 22, 2024
20 checks passed
@sophimao sophimao deleted the agilex_hetero_diag branch July 22, 2024 14:34
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.

2 participants