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

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

From
JHJeff Hostetler <git@jeffhostetler.com>
Date
Aug 7, 2023, 18:25 UTC
Message-ID
<2a490e5a-2e14-206b-f4ca-73e73e84cf74@jeffhostetler.com>
In-Reply-To
<2f39e481-84d1-097c-ec47-5357dbc36798@drbeat.li>
On 7/25/23 7:03 PM, Beat Bolli wrote:
Show 36 quoted lines
> On 25.07.23 21:31, Junio C Hamano wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> I also spotted this change since v1:
>>>
>>> - Rename trace2 counters to use "-" (not "_") as inter-word separators.
>>>
>>> Since I do not seem to be able to find any review comments regarding
>>> the variable naming in the v1's thread, let's ask stakeholders.
>>>
>>> Are folks involved in the trace2 subsystem (especially Jeff
>>> Hostetler---already CC:ed---who presumably has the most stake in it)
>>> OK with the naming convention of the multi-word variable?  This is
>>> the first use of multi-word variable name in tr2_ctr, and thus will
>>> establish whatever convention you guys want to use.  I do have a
>>> slight preference of "writeout-only" over "writeout_only" but that
>>> is purely from visual appearance.  If there is a desire to keep the
>>> names literally reusable as identifiers in some languages used to
>>> postprocess trace output, or something, that might weigh
>>> differently.
>>
>> I heard absolutely nothing since I asked the above question last
>> week, so I'll take the absense of response as absense of interest in
>> the way how names are spelled.
>>
>> Therefore, let me make a unilateral declaration here ;-)  The trace2
>> counters with multi-word names are to be named using "-" as their
>> inter-word separators.  Any patch that adds new counters that do not
>> follow the convention will silently dropped on the floor from now on.
>>
>> Let's move this patch forward by merging to 'next' soonish.
> 
> Works for me :-)
> 
> Cheers!
> 
Agreed.

Thanks Jeff

Previous: Beat BolliNext: Jeff Hostetler
Message 8 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.