-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
vulkan : do not use tensor->extra #9407
Conversation
This patch allows using the Vulkan backend with the RPC backend as tensor->extra is no longer used. Ref: ggerganov#8536
I have tested this by verifying that If you are OK with the proposed refactoring, I will also update the code surrounded by |
@ggerganov @rgerganov Apologies for the delay, I'm inbetween jobs and moving to a new city, so my time is rather limited. I'll try to find time to take care of the PRs waiting for my review this week. |
Thanks, no worries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nice, thank you. It cleans up some of the leftover code from previous iterations. It worked in my tests.
The only issue is that it breaks the GGML_VULKAN_CHECK_RESULTS
mode. Can you take a look at that or would you like me to?
@rgerganov I fixed the issue in rgerganov#2 |
Sorry for the delay, somehow I missed the notifications for this PR. Changes look good and merged. |
this should be good to go |
* vulkan : do not use tensor->extra This patch allows using the Vulkan backend with the RPC backend as tensor->extra is no longer used. Ref: ggerganov#8536 * Adapt GGML_VULKAN_CHECK_RESULTS to extra removal (Mobile-Artificial-Intelligence#2) --------- Co-authored-by: 0cc4m <[email protected]>
This patch allows using the Vulkan backend with the RPC backend as tensor->extra is no longer used.
Ref: #8536