kv-cache : simplify the interface #13660
Merged
+89
−153
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.
First part of some KV cache interface refactoring and simplification.
Public API changes
llama_kv_self_n_tokens
llama_kv_self_used_cells
Internal
llama_kv_cache
changesllama_kv_cache::get_n_tokens()
llama_kv_cache::get_used_cells()
llama_kv_cache::get_pos_max()
n_seq_max
to the KV cache objects. Will be needed later for improving the data structures for tracking the per-sequence information.type_k
andtype_v
memberspadding
->n_pad
for consistencyOther changes
llama_decode()
now verifies that if the input batch haspos == null
it should also haveseq_id == null
so that we can automatically assign all tokens toseq_id == 0
starting from the max position currently in the cache. This fixes/prevents an edge case where a batch withpos == null
that also has tokens withseq_id != 0
would be assigned incorrect positions by thellama_batch_allocr
./metrics
endpoint. These are too internal and implementation-specific and should not be exposed to the public.