Skip to content

Removing unused n_buffers and buffers fields from ggml_metal_context #5129

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
Jan 26, 2024
Merged

Removing unused n_buffers and buffers fields from ggml_metal_context #5129

merged 1 commit into from
Jan 26, 2024

Conversation

ptsochantaris
Copy link
Collaborator

I think that, from what I can make out, the n_buffers and buffers fields from ggml_metal_context are always 0 and nil, so they can just be removed, along with the ggml_metal_buffer type for the buffers array.

The ggml_metal_get_buffer is also trimmed down as it doesn't have two code paths anymore.

There are no performance benefits with this change (or rather, negligible benefits) but it's always nice to have less code to worry about.

@ggerganov ggerganov merged commit 6dd3c28 into ggml-org:master Jan 26, 2024
@ptsochantaris ptsochantaris deleted the removing-unused-ggml-metal-fields branch January 26, 2024 18:30
jordankanter pushed a commit to jordankanter/llama.cpp that referenced this pull request Feb 3, 2024
hodlen pushed a commit to hodlen/llama.cpp that referenced this pull request Apr 1, 2024
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.

4 participants