-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Upgrade init_tensor API to return a ggml_status #11854
base: master
Are you sure you want to change the base?
Conversation
150ffe8
to
d12a712
Compare
@slaren review please. Tks. |
d12a712
to
1205554
Compare
Tks @slaren |
29998fc
to
e2486eb
Compare
To prepare for an 'abort-free' ggml (ggml not to abort on OOMs but return a OOM status), as agreeed with Diego in the ggml repo, upgrade the init_tensor() and view_init() APIs to return a ggml_status.
e2486eb
to
51a0f6c
Compare
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.
ok, so ggml_backend_*_buffer_init_tensor
can only return success for most backends but since it's called through the interface init_tensor pointer they still need to return success. was the plan to eventually make cuda_init_tensor
sometimes return an error?
Tks @graehl
Yes but that a another PR in the ggml repo |
@slaren reready for review please. Best. |
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.
Good step forward towards the goal of returning an error instead of crashing.
To prepare for an 'abort-free' ggml, as agreeed with Diego in the ggml repo, upgrade the backend init_tensor APIs to return a ggml_status.
Make sure to read the contributing guidelines before submitting a PR