From: John Garry <john.g.garry@oracle.com>
To: Ian Rogers <irogers@google.com>, Will Deacon <will@kernel.org>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
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>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Kim Phillips <kim.phillips@amd.com>,
Florian Fischer <florian.fischer@muhq.space>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Xing Zhengjun <zhengjun.xing@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Kang Minchul <tegongkang@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Sandipan Das <sandipan.das@amd.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
linuxppc-dev@lists.ozlabs.org, Kajol Jain <kjain@linux.ibm.com>
Cc: Perry Taylor <perry.taylor@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v2 8/9] perf jevents: Generate metrics and events as separate tables
Date: Mon, 23 Jan 2023 15:18:19 +0000 [thread overview]
Message-ID: <f5d0e9f0-7076-07f5-483b-57eaee26ff3f@oracle.com> (raw)
In-Reply-To: <20221221223420.2157113-9-irogers@google.com>
On 21/12/2022 22:34, Ian Rogers wrote:
> Turn a perf json event into an event, metric or both. This reduces the
> number of events needed to scan to find an event or metric. As events
> no longer need the relatively seldom used metric fields, 4 bytes is
> saved per event. This reduces the big C string's size by 335kb (14.8%)
> on x86.
>
> Signed-off-by: Ian Rogers<irogers@google.com>
It would have been good to show an example of how the output changes. I
could not apply the series (see cover), and knowing what to expect makes
reviewing the code easier...
Thanks,
John
next prev parent reply other threads:[~2023-01-23 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 22:34 [PATCH v2 0/9] jevents/pmu-events improvements Ian Rogers
2022-12-21 22:34 ` [PATCH v2 1/9] perf jevents metric: Correct Function equality Ian Rogers
2022-12-21 22:34 ` [PATCH v2 2/9] perf jevents metric: Add ability to rewrite metrics in terms of others Ian Rogers
2022-12-21 22:34 ` [PATCH v2 3/9] perf jevents: Rewrite metrics in the same file with each other Ian Rogers
2022-12-21 22:34 ` [PATCH v2 4/9] perf pmu-events: Separate metric out of pmu_event Ian Rogers
2023-01-23 15:15 ` John Garry
2023-01-24 4:39 ` Ian Rogers
2022-12-21 22:34 ` [PATCH v2 5/9] perf stat: Remove evsel metric_name/expr Ian Rogers
2023-01-23 14:42 ` John Garry
2022-12-21 22:34 ` [PATCH v2 6/9] perf jevents: Combine table prefix and suffix writing Ian Rogers
2022-12-21 22:34 ` [PATCH v2 7/9] perf pmu-events: Introduce pmu_metrics_table Ian Rogers
2023-01-23 15:35 ` John Garry
2023-01-24 4:48 ` Ian Rogers
2022-12-21 22:34 ` [PATCH v2 8/9] perf jevents: Generate metrics and events as separate tables Ian Rogers
2023-01-23 15:18 ` John Garry [this message]
2023-01-24 4:49 ` Ian Rogers
2022-12-21 22:34 ` [PATCH v2 9/9] perf jevents: Add model list option Ian Rogers
2023-01-19 15:54 ` [PATCH v2 0/9] jevents/pmu-events improvements Ian Rogers
2023-01-23 13:25 ` John Garry
2023-01-24 5:04 ` Ian Rogers
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=f5d0e9f0-7076-07f5-483b-57eaee26ff3f@oracle.com \
--to=john.g.garry@oracle.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=florian.fischer@muhq.space \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kim.phillips@amd.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=robh@kernel.org \
--cc=sandipan.das@amd.com \
--cc=tegongkang@gmail.com \
--cc=will@kernel.org \
--cc=zhengjun.xing@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).