From: Junio C Hamano <gitster@pobox.com>
To: Josh Steadmon <steadmon@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] send-pack: add new tracing regions for push
Date: Thu, 22 Aug 2024 13:30:59 -0700 [thread overview]
Message-ID: <xmqq5xrsqozg.fsf@gitster.g> (raw)
In-Reply-To: <jjnfnxuozlsguonviswt23simi4gwqjaetcm7b7wn7kndk6o4t@7p4dedarn6xt> (Josh Steadmon's message of "Thu, 22 Aug 2024 13:20:46 -0700")
Josh Steadmon <steadmon@google.com> writes:
>> ... understandable if there weren't any suitable mechanism to simply log
>> "the control passed at this spot at this time" kind of event in the
>> trace2 subsystem, but I do not think it is the case.
>
> Ack, changed this to a "trace2_printf()" instead. Annoyingly the JSON
> Event trace2 target that we use at $DAYJOB doesn't log these events, but
> I can add another patch to enable that.
Ahh, OK, I was concentrating solely on the producing side, and
forgot to consider that the consuming side may not be prepared for
non enter/leave pair of events. That's understandable, but if you
are updating the consuming side to be able to do so, that would be
even better.
> Yeah, thanks, this did need to be reworked. I pushed the regions down
> into pack_objects() and receive_status(), which look like the only two
> places we might spend much time.
Sounds good.
This is a tangent, but I doubt we have many users without sideband
support. In the longer term we may be able to drop the non-sideband
codepath, which would automatically simplify the flow quite a bit
around here. But that is totally outside of this topic.
Thanks.
next prev parent reply other threads:[~2024-08-22 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 18:51 [PATCH 0/2] Add additional trace2 regions for fetch and push Josh Steadmon
2024-08-15 18:51 ` [PATCH 1/2] fetch: add top-level trace2 regions Josh Steadmon
2024-08-15 19:47 ` Junio C Hamano
2024-08-19 18:26 ` Josh Steadmon
2024-08-15 18:51 ` [PATCH 2/2] send-pack: add new tracing regions for push Josh Steadmon
2024-08-15 20:06 ` Junio C Hamano
2024-08-22 20:20 ` Josh Steadmon
2024-08-22 20:30 ` Junio C Hamano [this message]
2024-08-22 21:57 ` [PATCH v2 0/3] Add additional trace2 regions for fetch and push Josh Steadmon
2024-08-22 21:57 ` [PATCH v2 1/3] trace2: implement trace2_printf() for event target Josh Steadmon
2024-08-22 21:57 ` [PATCH v2 2/3] fetch: add top-level trace2 regions Josh Steadmon
2024-08-22 21:57 ` [PATCH v2 3/3] send-pack: add new tracing regions for push Josh Steadmon
2024-08-22 22:10 ` [PATCH v2 0/3] Add additional trace2 regions for fetch and push Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5xrsqozg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=steadmon@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.