From: Yang Jihong <yangjihong1@huawei.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [RFC 06/13] perf kwork: Implement perf kwork report
Date: Wed, 15 Jun 2022 11:12:16 +0800 [thread overview]
Message-ID: <2953080a-a1bd-0a1c-8466-96c4b58de2e6@huawei.com> (raw)
In-Reply-To: <CAM9d7ci9R4=LuyDJAHSqtxc3nOZG+N8e7_WKJUKtL5j3xXqqtA@mail.gmail.com>
Hello,
On 2022/6/15 5:49, Namhyung Kim wrote:
> On Mon, Jun 13, 2022 at 2:48 AM Yang Jihong <yangjihong1@huawei.com> wrote:
>>
>> Implements framework of perf kwork report, which is used to report time
>> properties such as run time and frequency:
>>
>> test case:
>>
>> Kwork Name | Cpu | Avg delay | Frequency | Max delay | Max delay start | Max delay end |
>> ---------------------------------------------------------------------------------------------------------------------------
>> ---------------------------------------------------------------------------------------------------------------------------
>>
>> Since there are no report supported events, the output is empty.
>>
>> Briefly describe the data structure:
>> 1. "class" indicates event type. For example, irq and softiq correspond
>> to different types.
>> 2. "cluster" refers to a specific event corresponding to a type. For
>> example, RCU and TIMER in softirq correspond to different clusters,
>> which contains three types of events: raise, entry, and exit.
>
> I'm not good at naming but how about calling it "work" instead?
> It's all about kernel works anyway..
>
How about calling it "work_atoms" ?
Otherwise, "work" feels a little similar to kwork_class in the first step.
Thanks,
Jihong
.
next prev parent reply other threads:[~2022-06-15 3:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 9:45 [RFC 00/13] perf: Add perf kwork Yang Jihong
2022-06-13 9:45 ` [RFC 01/13] perf kwork: New tool Yang Jihong
2022-06-14 21:43 ` Namhyung Kim
2022-06-15 1:38 ` Yang Jihong
2022-06-13 9:45 ` [RFC 02/13] perf kwork: Add irq record support Yang Jihong
2022-06-13 9:45 ` [RFC 03/13] perf kwork: Add softirq " Yang Jihong
2022-06-13 9:45 ` [RFC 04/13] perf kwork: Add workqueue " Yang Jihong
2022-06-13 9:45 ` [RFC 05/13] tools lib: Add list_last_entry_or_null Yang Jihong
2022-06-13 9:45 ` [RFC 06/13] perf kwork: Implement perf kwork report Yang Jihong
2022-06-14 21:49 ` Namhyung Kim
2022-06-15 3:12 ` Yang Jihong [this message]
2022-06-15 22:01 ` Namhyung Kim
2022-06-16 1:31 ` Yang Jihong
2022-06-13 9:45 ` [RFC 07/13] perf kwork: Add irq report support Yang Jihong
2022-06-13 9:46 ` [RFC 08/13] perf kwork: Add softirq " Yang Jihong
2022-06-13 9:46 ` [RFC 09/13] perf kwork: Add workqueue " Yang Jihong
2022-06-14 21:54 ` Namhyung Kim
2022-06-15 3:22 ` Yang Jihong
2022-06-15 21:56 ` Namhyung Kim
2022-06-16 1:42 ` Yang Jihong
2022-06-13 9:46 ` [RFC 10/13] perf kwork: Implement perf kwork latency Yang Jihong
2022-06-13 9:46 ` [RFC 11/13] perf kwork: Add softirq latency support Yang Jihong
2022-06-13 9:46 ` [RFC 12/13] perf kwork: Add workqueue " Yang Jihong
2022-06-13 9:46 ` [RFC 13/13] perf kwork: Implement perf kwork timehist Yang Jihong
2022-06-22 14:59 ` [RFC 00/13] perf: Add perf kwork Paul A. Clarke
2022-06-23 1:02 ` Yang Jihong
2022-06-23 14:25 ` Paul A. Clarke
2022-06-24 1:26 ` Yang Jihong
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=2953080a-a1bd-0a1c-8466-96c4b58de2e6@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®