Message ID | pull.1373.v4.git.1666618868.gitgitgadget@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Trace2 timers and counters and some cleanup | expand |
On 10/24/2022 9:40 AM, Jeff Hostetler via GitGitGadget wrote: > Here is version 4 of this series to add timers and counters to Trace2. > > Changes since V3: > > * Fixed typo in the new thread-name documentation. > * Use a simpler NS_TO_SEC() macro for reporting the timer values. > > Jeff Hostetler (8): > trace2: use size_t alloc,nr_open_regions in tr2tls_thread_ctx > tr2tls: clarify TLS terminology > api-trace2.txt: elminate section describing the public trace2 API > trace2: rename the thread_name argument to trace2_thread_start > trace2: improve thread-name documentation in the thread-context > trace2: convert ctx.thread_name from strbuf to pointer > trace2: add stopwatch timers > trace2: add global counter mechanism I re-read the series as well as looked at the range-diffs for the previous two versions. I continue to think this is a high-quality series and I've used it multiple times in my personal development workflow to investigate certain performance things. I'm looking forward to this being merged so we can all use it. Thanks, -Stolee
Derrick Stolee <derrickstolee@github.com> writes: > On 10/24/2022 9:40 AM, Jeff Hostetler via GitGitGadget wrote: >> Here is version 4 of this series to add timers and counters to Trace2. >> >> Changes since V3: >> >> * Fixed typo in the new thread-name documentation. >> * Use a simpler NS_TO_SEC() macro for reporting the timer values. >> >> Jeff Hostetler (8): >> trace2: use size_t alloc,nr_open_regions in tr2tls_thread_ctx >> tr2tls: clarify TLS terminology >> api-trace2.txt: elminate section describing the public trace2 API >> trace2: rename the thread_name argument to trace2_thread_start >> trace2: improve thread-name documentation in the thread-context >> trace2: convert ctx.thread_name from strbuf to pointer >> trace2: add stopwatch timers >> trace2: add global counter mechanism > > I re-read the series as well as looked at the range-diffs for the > previous two versions. I continue to think this is a high-quality > series and I've used it multiple times in my personal development > workflow to investigate certain performance things. I'm looking > forward to this being merged so we can all use it. I agree with your assessment. Let's move it forward. Thanks, all.