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

Re: [PATCH 2/2] wrapper: use trace2 counters to collect fsync stats

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 20, 2023, 00:12 UTC
Message-ID
<xmqqbkg75tkm.fsf@gitster.g>
In-Reply-To
<20230719232444.555838-2-dev+git@drbeat.li>
Beat Bolli <dev+git@drbeat.li> writes:
Show 17 quoted lines
> As mentioned in the subthread starting at [1], trace2 counters should be
> used to count events instead of ad-hoc static variables.
>
> Convert the static variables that count fsync calls to trace2 counters,
> reducing the coupling between wrapper.c and the trace2 subsystem.
>
> The counters are not per-thread because the ones being replaced also
> were not.
>
> [1] https://lore.kernel.org/git/20230627195251.1973421-2-calvinwan@google.com/
>
> Signed-off-by: Beat Bolli <dev+git@drbeat.li>
> ---
> I have based this series on master, so this patch will create a trivial
> merge conflict with c489f47a649d (refs/packed-backend.c: add trace2
> counters for jump list, 2023-07-10) on next, which also adds a new
> counter.

Thanks for leaving a note. This one was trivial enough to resolve, but it is a good discipline to always make trial merges to 'next' and with other topics in flight.

Did t5351 pass for you with this patch? Any other test breakages that the patch needs to also adjust?

Thanks.
Previous: Beat BolliNext: Beat Bolli
Message 3 of 9 in “trace2: fix a comment”
  1. 1/2 trace2: fix a commentBeat Bolli, Jul 19, 2023
  2. 2/2 wrapper: use trace2 counters to collect fsync statsBeat Bolli, Jul 19, 2023
  3. Junio C HamanoJul 20, 2023
  4. 2/2 wrapper: use trace2 counters to collect fsync statsBeat Bolli, Jul 20, 2023
  5. Junio C HamanoJul 20, 2023
  6. Junio C HamanoJul 25, 2023
  7. Beat BolliJul 25, 2023
  8. Jeff HostetlerAug 7, 2023
  9. Jeff HostetlerAug 7, 2023

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.