From: "Du, Changbin" <changbin.du@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
changbin.du@intel.com, peterz@infradead.org, mingo@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf sched map: re-annotate shortname if thread comm changed
Date: Wed, 7 Mar 2018 10:28:57 +0800 [thread overview]
Message-ID: <20180307022857.kqxmo24we5r54nlh@intel.com> (raw)
In-Reply-To: <20180306141707.GG10176@kernel.org>
On Tue, Mar 06, 2018 at 11:17:07AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 06, 2018 at 08:53:02AM +0100, Jiri Olsa escreveu:
> > On Tue, Mar 06, 2018 at 11:37:35AM +0800, changbin.du@intel.com wrote:
> > > From: Changbin Du <changbin.du@intel.com>
> > >
> > > v2:
> > > o add a patch to move thread::shortname to thread_runtime
> > > o add function perf_sched__process_comm() to process PERF_RECORD_COMM event.
> > >
> > > Changbin Du (2):
> > > perf sched: move thread::shortname to thread_runtime
> > > perf sched map: re-annotate shortname if thread comm changed
> >
> > Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> Thanks, applied both, the final layout for 'struct thread_runtime':
>
> [root@jouet perf]# pahole -C thread_runtime ~/bin/perf
> struct thread_runtime {
> u64 last_time; /* 0 8 */
> u64 dt_run; /* 8 8 */
> u64 dt_sleep; /* 16 8 */
> u64 dt_iowait; /* 24 8 */
> u64 dt_preempt; /* 32 8 */
> u64 dt_delay; /* 40 8 */
> u64 ready_to_run; /* 48 8 */
> struct stats run_stats; /* 56 40 */
> /* --- cacheline 1 boundary (64 bytes) was 32 bytes ago --- */
> u64 total_run_time; /* 96 8 */
> u64 total_sleep_time; /* 104 8 */
> u64 total_iowait_time; /* 112 8 */
> u64 total_preempt_time; /* 120 8 */
> /* --- cacheline 2 boundary (128 bytes) --- */
> u64 total_delay_time; /* 128 8 */
> int last_state; /* 136 4 */
> char shortname[3]; /* 140 3 */
> _Bool comm_changed; /* 143 1 */
> u64 migrations; /* 144 8 */
>
> /* size: 152, cachelines: 3, members: 17 */
> /* last cacheline: 24 bytes */
> };
> [root@jouet perf]#
Hi Arnaldo, thanks for your patient optimization for this!
--
Thanks,
Changbin Du
prev parent reply other threads:[~2018-03-07 2:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 3:37 changbin.du
2018-03-06 3:37 ` [PATCH v2 1/2] perf sched: move thread::shortname to thread_runtime changbin.du
2018-03-06 14:09 ` Arnaldo Carvalho de Melo
2018-03-07 2:44 ` Namhyung Kim
2018-03-09 8:37 ` [tip:perf/core] perf sched: Move " tip-bot for Changbin Du
2018-03-06 3:37 ` [PATCH v2 2/2] perf sched map: re-annotate shortname if thread comm changed changbin.du
2018-03-09 8:37 ` [tip:perf/core] perf sched map: Re-annotate " tip-bot for Changbin Du
2018-03-06 7:53 ` [PATCH v2 0/2] perf sched map: re-annotate " Jiri Olsa
2018-03-06 14:17 ` Arnaldo Carvalho de Melo
2018-03-07 2:28 ` Du, Changbin [this message]
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=20180307022857.kqxmo24we5r54nlh@intel.com \
--to=changbin.du@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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®