LumpiastyandClaude Opus 5.5 53d2828bb5 llama: inkling2_loop - per-pass views of host weights for the later loop passes
inkling2_loop runs the core layers (6..17 on Inkling-2-Mini) three times, and
post_arch_tensors makes every cache slot share the tensors of its physical
layer. With the experts in host memory (--n-cpu-moe, -ot exps=CPU) the
scheduler makes one device copy per (host tensor, backend) per graph, at the
first split that reads it, and keeps it until the last reader. So:

- the expert copies of all 12 loop layers are alive at once (about 6.5 GiB on
  UD-Q4_K_XL), which is most of the ~7 GiB Vulkan0 compute buffer;
- sched_copy_experts runs only for the first reader. When it reads the ids back
  (ubatches of 32-63 tokens: MUL_MAT_ID is offloaded from 32 tokens, the F1
  skip starts at 4*n_expert ids), it uploads only the experts that pass 0
  selected, and passes 1 and 2 read stale VRAM for the others (upstream issue
  #32755, "GGGG" output).

Add a post_load_tensors hook to llama_model (called after the weights are
loaded, and on the no_alloc path after the dummy buffers are set). In
inkling2_loop it replaces, for each slot of a later pass, every tensor in a
host buffer with a view of it (name "<name>.visit<pass>", buffer and data of
the original). The scheduler hashes tensors by pointer, so each pass gets its
own copy, freed after that pass, and the copy callback sees the ids of that
pass. Weights in device buffers and CPU extra buffers (CPU_REPACK, not host)
stay shared. The pointer-keyed weight maps (w_scales, prec_policy, hdmd.rot)
get entries for the views. The views live in a model-owned context outside
ctxs_bufs, so the F4 release/restore, tensor counts and the memory breakdown
do not see them; they point only at host buffers, which F4 never releases.

LLAMA_LOOP_HOST_VIEWS=0 keeps the shared tensors (A/B knob).

Not built or run yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PZz44SLQvTXMyWGio6t9DZ
2026-11-22 20:38:33 +01:00
2026-06-12 15:53:26 +02:00
2026-10-17 02:11:56 +02:00
2026-11-16 13:28:31 +02:00
2026-11-17 11:04:12 +02:00
2026-02-02 08:38:55 +02:00

llama.cpp

llama.cpp

Description

The main goal of llama.cpp is to enable LLM (and MLLM) inference with minimal setup and state-of-the-art performance on a wide range of hardware - locally and in the cloud.

The llama.cpp project is built on top of the ggml library.

This fork - RX 580 (Polaris / GCN) serving of large MoE models

A private fork maintained for one machine: an AMD RX 580 8 GB (RADV Vulkan) serving Qwen3.6-35B-A3B, gemma-4-26B-A4B and smaller models under llama-swap, with the MoE experts in host RAM (--n-cpu-moe). FORK.md is the source of truth: every fork change with its invariants, rebase hazards and validation, the measured dead ends, the production configuration and the measurement traps. The rebase and deploy procedure is docs/fork-rebase-runbook.md; scripts/fork-validate.sh validates a build against a reference; scripts/rx580-bench/ is the benchmark harness.

In short, the fork adds:

  • three Polaris prefill wins, on without a flag and token-identical to mainline: the MoE routing-ids readback skip in sched_copy_experts, flash-attention mask_opt for GCN at head size >= 256, and a tiled-transpose fast path for the delta-net conv-state concat;
  • opt-in VRAM time-sharing between several llama-server processes (LLAMA_SLEEP_VRAM_ONLY, LLAMA_SLEEP_EVICT_KV, LLAMA_MMPROJ_ONDEMAND, LLAMA_VRAM_ARENA): a model releases everything it holds in VRAM and gets it back without a restart, so its RAM prompt cache survives;
  • fixes to the server's sleep, wake and shutdown paths and to cold teardown that the sharing exposed;
  • validation-only env knobs (GGML_VK_CONCAT_FASTPATH, LLAMA_MOE_IDS_SKIP), unset in production.

Production settings for the 35B are in FORK.md section 5 (-lm none -t 6 -ngl 99 --n-cpu-moe 40 -b 2048 -ub 2048 -fa 1 --parallel 1, ctx 131072). Keep all experts on the host (--n-cpu-moe 40) for long contexts: lower values are faster only at short context and run out of VRAM as the KV grows (FORK.md section 4).

Quick start

A few options to get llama.cpp installed on your machine:

# curl
curl -LsSf https://llama.app/install.sh | sh

# powershell
irm https://llama.app/install.ps1 | iex

Once installed:

# Download and run a model directly from Hugging Face
llama cli -hf ggml-org/Qwen3.5-0.8B-GGUF

# Launch OpenAI-compatible API server
llama serve -hf ggml-org/Qwen3.5-0.8B-GGUF
VLM session with `llama cli` VLM session with llama cli Llama Chat, the built-in chat app, against `llama serve` running Qwen 3.6 Llama Chat, the built-in chat app, against llama serve

Documentation

Tools

Development

Contributing

  • Contributors can open PRs
  • Collaborators will be invited based on contributions
  • Maintainers can push to branches in the llama.cpp repo and merge PRs into the master branch
  • Any help with managing issues, PRs and projects is very appreciated!
  • Read the CONTRIBUTING.md for more information

Acknowledgements

  • yhirose/cpp-httplib - Single-header HTTP server, used by llama-server - MIT license
  • nothings/stb - Single-header image format decoder, used by multimodal subsystem - Public domain
  • nlohmann/json - Single-header JSON library, used by various tools/examples - MIT License
  • mackron/miniaudio - Single-header audio format decoder, used by multimodal subsystem - Public domain
  • sheredom/subprocess.h - Single-header process launching solution for C and C++ - Public domain
S
Description
No description provided
Readme MIT
584 MiB
0 Stars 1 Watchers 0 Forks
Languages
C++ 54.9%
C 16.7%
Python 7%
Cuda 5.6%
TypeScript 3.9%
Other 11.7%