b10145

ggml-org/llama.cppb10145Jul 27, 2026by github-actions[bot]same day as b10144

What changed since b10144

high risk

b10145 reverts --mlock to lock memory in place without memory mapping, undoing the previous flag semantics.

Breaking changes

  • --mlock no longer implies mmap-backed loading; it now mlocks non-mmap'ed memory, so scripts relying on the b10144 behavior will see different memory usage and load paths.

New features

  • An explicit mlock option is documented for locking non-mmap'ed memory, making the intended behavior selectable rather than implicit.

Improvements

  • CLI argument documentation was updated to describe the corrected --mlock semantics.
  • Benchmark and docs churn from the change was cleaned up before merge.

Upgrade notes

If your launch scripts pass --mlock and depend on memory-mapped loading, re-check memory footprint and OOM behavior after upgrading, since the flag now locks non-mmap'ed memory instead. Review the updated CLI docs for the mlock option and adjust flags accordingly. The server/UI stream and session fixes from b10144 are unchanged and carry over.

Analyzed Nov 1, 2026

Upgrading?

Release notes summary

Modified the --mlock flag behavior to exclusively lock memory in place without memory mapping.

Key Highlights

  • Clarified --mlock behavior to lock memory without memory mapping

Release Notes (excerpt)

<details open> args: add `-lm mlock` where it mlocks but doesnt mmap (#26135) * arg: add `-lm mlock` where it mlocks but doesnt mmap Signed-off-by: Aaron Teo <aaron.teo1@ibm.com> * docs: rm unwanted docs changes Signed-off-by: Aaron Teo <aaron.teo1@ibm.com> * docs: revert auto-formatting Signed-off-by: Aaron Teo <aaron.teo1@ibm.com> * bench: fix automated review point 3 Signed-off-by: Aaron Teo <aaron.teo1@ibm.com> * arg: revert the meaning of --mlock to non-mmap'ed mlock…

Published by ggml-org on GitHub.

Read the full release notes

Related Repositories