git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] status: stop holding index.lock while collecting

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 23, 2026, 18:33 UTC
Message-ID
<xmqqik2s5kt3.fsf@gitster.g>
In-Reply-To
<20261022184420.3648771-1-mcosma@gmail.com>
Mihai Cosma <mcosma@gmail.com> writes:
Show 7 quoted lines
> This overlaps with Jun Wu's "Wait for the index lock instead of
> failing" series, and the two fit together: his makes writers wait for
> the lock, this makes status hold it rarely and briefly. They only
> conflict on the one lock call in cmd_status(), which his series renames
> to repo_try_hold_locked_index(). I'm happy to rebase onto it. On top of
> his v2, the slowest "git add" in the clean case below went from 1020 ms
> (one failure at his 1s timeout) to 160 ms.
Perhaps you two can work together and send a single consolidated series?
Thanks.
Previous: Mihai CosmaNext: Jun Wu
Message 4 of 5 in “status: stop holding index.lock while collecting”
  1. 0/2 status: stop holding index.lock while collectingMihai Cosma, Oct 22, 2026
  2. 1/2 read-cache: verify skipHash index by stat dataMihai Cosma, Oct 22, 2026
  3. 2/2 status: lock the index only to write itMihai Cosma, Oct 22, 2026
  4. Junio C HamanoOct 23, 2026
  5. Jun WuOct 23, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.