[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ea108115-f2dd-5767-1f86-34cdfdedc2a5@huawei.com>
Date: Fri, 5 Aug 2022 09:11:21 +0100
From: John Garry <john.garry@...wei.com>
To: Ian Rogers <irogers@...gle.com>
CC: Will Deacon <will@...nel.org>, James Clark <james.clark@....com>,
"Mike Leach" <mike.leach@...aro.org>, Leo Yan <leo.yan@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
"Arnaldo Carvalho de Melo" <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Alexander Shishkin" <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Andi Kleen <ak@...ux.intel.com>,
"Zhengjun Xing" <zhengjun.xing@...ux.intel.com>,
Ravi Bangoria <ravi.bangoria@....com>,
Kan Liang <kan.liang@...ux.intel.com>,
Adrian Hunter <adrian.hunter@...el.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-perf-users@...r.kernel.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH v3 00/17] Compress the pmu_event tables
On 02/08/2022 10:08, John Garry wrote:
>
>
>> we can ignore the costs of the strings as
>> they should be fully shared, especially for BDW-DE.
>
> Are you sure about this? I did not think that the compiler would have
> the intelligence to try to share strings. That is the basis of the size
> optimisation which I was proposing (that the compiler would not share
> strings).
JFYI, I am finding that all identical strings are shared, which is good.
Thanks,
John
Powered by blists - more mailing lists