Skip to content

[AsyncAlloc][SYCL][ABI-BREAK] Use the SYCL properties extension for memory pool creation #17955

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 12 commits into from
Jun 18, 2025

Conversation

Seanst98
Copy link
Contributor

Introduce initial_threshold, maximum_size, read_only, and zero_init runtime properties conforming to the SYCL properties extension, and apply these properties to the creation of memory pools.

This PR is a draft until the feature has been added to the sycl_ext_oneapi_async_memory_alloc spec.

@Seanst98 Seanst98 force-pushed the sean/async-alloc-properties-ext branch from dcb5523 to 8712e9f Compare April 10, 2025 12:36
@omarahmed1111 omarahmed1111 marked this pull request as ready for review May 23, 2025 14:09
@omarahmed1111 omarahmed1111 requested a review from a team as a code owner May 23, 2025 14:09
@omarahmed1111 omarahmed1111 requested a review from againull May 23, 2025 14:09
…emory pool

creation

Introduce initial_threshold, maximum_size, read_only, and zero_init
runtime properties conforming to the SYCL properties extension, and
apply these properties to the creation of memory pools.
@againull
Copy link
Contributor

We are not allowed to break ABI outside of the window, is it possible to guard the breaking changes with __INTEL_PREVIEW_BREAKING_CHANGES macro?

@againull againull added the abi-break change that's breaking abi and waiting for the next window to be able to merge label May 23, 2025
@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from 8712e9f to b615655 Compare May 27, 2025 10:20
@omarahmed1111 omarahmed1111 requested a review from a team as a code owner May 27, 2025 10:20
@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from b615655 to 6171ed8 Compare May 27, 2025 13:41
@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from 6171ed8 to 599af2f Compare May 27, 2025 13:45
@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from 599af2f to b0e7b06 Compare May 27, 2025 14:23
@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from 7cd8ba7 to 5d77b23 Compare May 27, 2025 16:08
@againull
Copy link
Contributor

againull commented May 27, 2025

@omarahmed1111 @Seanst98 I'm very sorry, I completely missed that this is an experimental extension which has been just recently implemented (so, as far as I understand it hasn't even made it to the previous release). For experimental extensions it is allowed to break ABI, so initial version of the PR was good (i.e. there is no necessity to guard with __INTEL_PREVIEW_BREAKING_CHANGES). Again, really sorry for false alarm

@omarahmed1111 omarahmed1111 force-pushed the sean/async-alloc-properties-ext branch from 05164ff to f9761f8 Compare June 16, 2025 18:02
@againull againull merged commit 56d06a6 into intel:sycl Jun 18, 2025
24 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.

6 participants