SYCL: Avoid using SYCL-Graph for unsupported nodes #13587
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently on a CUDA backend to SYCL when running `GGML_SYCL_DISABLE_GRAPH=0 ./bin/test-backend-ops -b SYCL0` there are two operations that throw an exception from the blocking waits during queue recording. * `-o CONCAT` : Use of blocking waits on a queue that's being recorded https://github.com/ggml-org/llama.cpp/blob/master/ggml/src/ggml-sycl/concat.cpp#L185-L187 * `-o MUL_MAT_ID`: Blocking wait on a recording queue for a copy to host memory https://github.com/ggml-org/llama.cpp/blob/master/ggml/src/ggml-sycl/ggml-sycl.cpp#L3072-L3074 We've noticed that `ggml-cuda.cu` has the [check_node_graph_compatibility_and_refresh_copy_ops](https://github.com/ggml-org/llama.cpp/blob/39e73ae0d69f882d7e29cecc6dd8f5052fca6731/ggml/src/ggml-cuda/ggml-cuda.cu#L2458-L2458) method for checking if a graph can be used, even if enabled. I've taken a similar approach in this PR by adding a method to `ggml-sycl.cpp` for checking if a graph can be used for the operations even if a user has asked for it to be enabled.
github-actions
bot
added
ggml
EwanC
changed the title
Rbiessy
reviewed
May 19, 2025
Comment on lines
+3829
to
+3831
| # ifndef NDEBUG | ||
| GGML_LOG_DEBUG("%s: disabling SYCL graphs due to unsupported node type\n", __func__); | ||
| # endif |
There was a problem hiding this comment.
Nit but maybe worth having this as GGML_LOG_INFO and printing which node type is unsupported?
| @@ -3810,11 +3810,38 @@ static void ggml_backend_sycl_graph_compute_impl(ggml_backend_sycl_context * syc | |||
| } | |||
| } | |||
|
|
|||
| #ifdef GGML_SYCL_GRAPH | |||
| static bool check_node_graph_compatibility(ggml_cgraph * cgraph) { | |||
There was a problem hiding this comment.
CUDA checks if one of the buffer is split, meaning multiple devices are used, to disable the graph. I assume you don't test that, may be safe to disable it as well? Or do you expect SYCL-Graph would work well in such a case?
I'd suggest just checking if ggml_sycl_info().device_count > 1 to disable SYCL-Graph.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently on a CUDA backend to SYCL when running
GGML_SYCL_DISABLE_GRAPH=0 ./bin/test-backend-ops -b SYCL0there are two operations that throw an exception from the blocking waits during queue recording.-o CONCAT: Use of blocking waits on a queue that's being recorded in ggml_sycl_op_concat.-o MUL_MAT_ID: Blocking wait on a recording queue for a copy to host memory in ggml_sycl_mul_mat_id.We've noticed that
ggml-cuda.cuhas thecheck_node_graph_compatibility_and_refresh_copy_ops method for checking if a graph can be used, even if enabled. I've taken a similar approach in this PR by adding a method to
ggml-sycl.cppfor checking if a graph can be used for the operations even if a user has asked for it to be enabled.