From: Ian Rogers <irogers@google.com> To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>, Mark Rutland <mark.rutland@arm.com>, Alexander Shishkin <alexander.shishkin@linux.intel.com>, Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Suzuki K Poulose <suzuki.poulose@arm.com>, Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>, John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>, Alexei Starovoitov <ast@kernel.org>, Daniel Borkmann <daniel@iogearbox.net>, Andrii Nakryiko <andrii@kernel.org>, Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>, John Fastabend <john.fastabend@gmail.com>, KP Singh <kpsingh@kernel.org>, Kajol Jain <kjain@linux.ibm.com>, James Clark <james.clark@arm.com>, German Gomez <german.gomez@arm.com>, Adrian Hunter <adrian.hunter@intel.com>, Riccardo Mancini <rickyman7@gmail.com>, Andi Kleen <ak@linux.intel.com>, Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>, Alexander Antonov <alexander.antonov@linux.intel.com>, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org, bpf@vger.kernel.org, Stephane Eranian <eranian@google.com> Subject: Re: [PATCH 3/5] perf cpumap: Add intersect function. Date: Mon, 28 Mar 2022 14:25:21 -0700 [thread overview] Message-ID: <CAP-5=fV+DiB=_+R+g+FLgLOyY5q205OGjfsaZntVKFy4jM4rcg@mail.gmail.com> (raw) In-Reply-To: <CE94B4BA-5073-4332-A13E-2CD20379AA19@gmail.com> On Mon, Mar 28, 2022 at 2:00 PM Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote: > > > > On March 28, 2022 5:54:06 PM GMT-03:00, Ian Rogers <irogers@google.com> wrote: > >On Mon, Mar 28, 2022 at 1:28 PM Arnaldo Carvalho de Melo > ><acme@kernel.org> wrote: > >> > >> Em Sun, Mar 27, 2022 at 11:24:12PM -0700, Ian Rogers escreveu: > >> > The merge function gives the union of two cpu maps. Add an intersect > >> > function which will be used in the next change. > >> > > >> > Signed-off-by: Ian Rogers <irogers@google.com> > >> > --- > >> > tools/lib/perf/cpumap.c | 38 ++++++++++++++++++++++++++++ > >> > tools/lib/perf/include/perf/cpumap.h | 2 ++ > >> > 2 files changed, 40 insertions(+) > >> > > >> > diff --git a/tools/lib/perf/cpumap.c b/tools/lib/perf/cpumap.c > >> > index 953bc50b0e41..56b4d213039f 100644 > >> > --- a/tools/lib/perf/cpumap.c > >> > +++ b/tools/lib/perf/cpumap.c > >> > @@ -393,3 +393,41 @@ struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig, > >> > perf_cpu_map__put(orig); > >> > return merged; > >> > } > >> > + > >> > +struct perf_cpu_map *perf_cpu_map__intersect(struct perf_cpu_map *orig, > >> > + struct perf_cpu_map *other) > >> > +{ > >> > + struct perf_cpu *tmp_cpus; > >> > + int tmp_len; > >> > + int i, j, k; > >> > + struct perf_cpu_map *merged = NULL; > >> > + > >> > + if (perf_cpu_map__is_subset(other, orig)) > >> > + return orig; > >> > + if (perf_cpu_map__is_subset(orig, other)) { > >> > + perf_cpu_map__put(orig); > >> > >> Why this put(orig)? > > > >As with merge, if orig isn't returned then it is put. > > For merge I can see it dropping a reference, i.e. get b and merge it into a, after that b was "consumed" > > But for intersect? The current use case is the intersect of all online CPUs with the merge of all CPU maps from evsels. So we can generally just reuse all_cpus, or the common case of both maps contain every CPU. I think the pattern makes code like: evlist->cpus = perf_cpu_map__intersect(evlist->cpus, other); not quite as messy, as without the put you need: tmp = perf_cpu_map__intersect(evlist->cpus, other); perf_cpu_map__put(evlist->cpus); evlist->cpus = tmp; I'm somewhat agnostic on what the API should be, but it'd be nice if merge and intersect behaved in a similar way. Thanks, Ian > > > >> > + return perf_cpu_map__get(other); > >> > >> And why the get here and not on the first if? > > > >The first argument orig is either put or returned while the second may > >be returned only if the reference count is incremented. We could > >change the API for merge and intersect to put both arguments, or to > >not put either argument. > > > >Thanks, > >Ian > > > >> > + } > >> > + > >> > + tmp_len = max(orig->nr, other->nr); > >> > + tmp_cpus = malloc(tmp_len * sizeof(struct perf_cpu)); > >> > + if (!tmp_cpus) > >> > + return NULL; > >> > + > >> > + i = j = k = 0; > >> > + while (i < orig->nr && j < other->nr) { > >> > + if (orig->map[i].cpu < other->map[j].cpu) > >> > + i++; > >> > + else if (orig->map[i].cpu > other->map[j].cpu) > >> > + j++; > >> > + else { > >> > + j++; > >> > + tmp_cpus[k++] = orig->map[i++]; > >> > + } > >> > + } > >> > + if (k) > >> > + merged = cpu_map__trim_new(k, tmp_cpus); > >> > + free(tmp_cpus); > >> > + perf_cpu_map__put(orig); > >> > + return merged; > >> > +} > >> > diff --git a/tools/lib/perf/include/perf/cpumap.h b/tools/lib/perf/include/perf/cpumap.h > >> > index 4a2edbdb5e2b..a2a7216c0b78 100644 > >> > --- a/tools/lib/perf/include/perf/cpumap.h > >> > +++ b/tools/lib/perf/include/perf/cpumap.h > >> > @@ -19,6 +19,8 @@ LIBPERF_API struct perf_cpu_map *perf_cpu_map__read(FILE *file); > >> > LIBPERF_API struct perf_cpu_map *perf_cpu_map__get(struct perf_cpu_map *map); > >> > LIBPERF_API struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig, > >> > struct perf_cpu_map *other); > >> > +LIBPERF_API struct perf_cpu_map *perf_cpu_map__intersect(struct perf_cpu_map *orig, > >> > + struct perf_cpu_map *other); > >> > LIBPERF_API void perf_cpu_map__put(struct perf_cpu_map *map); > >> > LIBPERF_API struct perf_cpu perf_cpu_map__cpu(const struct perf_cpu_map *cpus, int idx); > >> > LIBPERF_API int perf_cpu_map__nr(const struct perf_cpu_map *cpus); > >> > -- > >> > 2.35.1.1021.g381101b075-goog > >> > >> -- > >> > >> - Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Ian Rogers <irogers@google.com> To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>, Mark Rutland <mark.rutland@arm.com>, Alexander Shishkin <alexander.shishkin@linux.intel.com>, Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Suzuki K Poulose <suzuki.poulose@arm.com>, Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>, John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>, Alexei Starovoitov <ast@kernel.org>, Daniel Borkmann <daniel@iogearbox.net>, Andrii Nakryiko <andrii@kernel.org>, Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>, John Fastabend <john.fastabend@gmail.com>, KP Singh <kpsingh@kernel.org>, Kajol Jain <kjain@linux.ibm.com>, James Clark <james.clark@arm.com>, German Gomez <german.gomez@arm.com>, Adrian Hunter <adrian.hunter@intel.com>, Riccardo Mancini <rickyman7@gmail.com>, Andi Kleen <ak@linux.intel.com>, Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>, Alexander Antonov <alexander.antonov@linux.intel.com>, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org, bpf@vger.kernel.org, Stephane Eranian <eranian@google.com> Subject: Re: [PATCH 3/5] perf cpumap: Add intersect function. Date: Mon, 28 Mar 2022 14:25:21 -0700 [thread overview] Message-ID: <CAP-5=fV+DiB=_+R+g+FLgLOyY5q205OGjfsaZntVKFy4jM4rcg@mail.gmail.com> (raw) In-Reply-To: <CE94B4BA-5073-4332-A13E-2CD20379AA19@gmail.com> On Mon, Mar 28, 2022 at 2:00 PM Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote: > > > > On March 28, 2022 5:54:06 PM GMT-03:00, Ian Rogers <irogers@google.com> wrote: > >On Mon, Mar 28, 2022 at 1:28 PM Arnaldo Carvalho de Melo > ><acme@kernel.org> wrote: > >> > >> Em Sun, Mar 27, 2022 at 11:24:12PM -0700, Ian Rogers escreveu: > >> > The merge function gives the union of two cpu maps. Add an intersect > >> > function which will be used in the next change. > >> > > >> > Signed-off-by: Ian Rogers <irogers@google.com> > >> > --- > >> > tools/lib/perf/cpumap.c | 38 ++++++++++++++++++++++++++++ > >> > tools/lib/perf/include/perf/cpumap.h | 2 ++ > >> > 2 files changed, 40 insertions(+) > >> > > >> > diff --git a/tools/lib/perf/cpumap.c b/tools/lib/perf/cpumap.c > >> > index 953bc50b0e41..56b4d213039f 100644 > >> > --- a/tools/lib/perf/cpumap.c > >> > +++ b/tools/lib/perf/cpumap.c > >> > @@ -393,3 +393,41 @@ struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig, > >> > perf_cpu_map__put(orig); > >> > return merged; > >> > } > >> > + > >> > +struct perf_cpu_map *perf_cpu_map__intersect(struct perf_cpu_map *orig, > >> > + struct perf_cpu_map *other) > >> > +{ > >> > + struct perf_cpu *tmp_cpus; > >> > + int tmp_len; > >> > + int i, j, k; > >> > + struct perf_cpu_map *merged = NULL; > >> > + > >> > + if (perf_cpu_map__is_subset(other, orig)) > >> > + return orig; > >> > + if (perf_cpu_map__is_subset(orig, other)) { > >> > + perf_cpu_map__put(orig); > >> > >> Why this put(orig)? > > > >As with merge, if orig isn't returned then it is put. > > For merge I can see it dropping a reference, i.e. get b and merge it into a, after that b was "consumed" > > But for intersect? The current use case is the intersect of all online CPUs with the merge of all CPU maps from evsels. So we can generally just reuse all_cpus, or the common case of both maps contain every CPU. I think the pattern makes code like: evlist->cpus = perf_cpu_map__intersect(evlist->cpus, other); not quite as messy, as without the put you need: tmp = perf_cpu_map__intersect(evlist->cpus, other); perf_cpu_map__put(evlist->cpus); evlist->cpus = tmp; I'm somewhat agnostic on what the API should be, but it'd be nice if merge and intersect behaved in a similar way. Thanks, Ian > > > >> > + return perf_cpu_map__get(other); > >> > >> And why the get here and not on the first if? > > > >The first argument orig is either put or returned while the second may > >be returned only if the reference count is incremented. We could > >change the API for merge and intersect to put both arguments, or to > >not put either argument. > > > >Thanks, > >Ian > > > >> > + } > >> > + > >> > + tmp_len = max(orig->nr, other->nr); > >> > + tmp_cpus = malloc(tmp_len * sizeof(struct perf_cpu)); > >> > + if (!tmp_cpus) > >> > + return NULL; > >> > + > >> > + i = j = k = 0; > >> > + while (i < orig->nr && j < other->nr) { > >> > + if (orig->map[i].cpu < other->map[j].cpu) > >> > + i++; > >> > + else if (orig->map[i].cpu > other->map[j].cpu) > >> > + j++; > >> > + else { > >> > + j++; > >> > + tmp_cpus[k++] = orig->map[i++]; > >> > + } > >> > + } > >> > + if (k) > >> > + merged = cpu_map__trim_new(k, tmp_cpus); > >> > + free(tmp_cpus); > >> > + perf_cpu_map__put(orig); > >> > + return merged; > >> > +} > >> > diff --git a/tools/lib/perf/include/perf/cpumap.h b/tools/lib/perf/include/perf/cpumap.h > >> > index 4a2edbdb5e2b..a2a7216c0b78 100644 > >> > --- a/tools/lib/perf/include/perf/cpumap.h > >> > +++ b/tools/lib/perf/include/perf/cpumap.h > >> > @@ -19,6 +19,8 @@ LIBPERF_API struct perf_cpu_map *perf_cpu_map__read(FILE *file); > >> > LIBPERF_API struct perf_cpu_map *perf_cpu_map__get(struct perf_cpu_map *map); > >> > LIBPERF_API struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig, > >> > struct perf_cpu_map *other); > >> > +LIBPERF_API struct perf_cpu_map *perf_cpu_map__intersect(struct perf_cpu_map *orig, > >> > + struct perf_cpu_map *other); > >> > LIBPERF_API void perf_cpu_map__put(struct perf_cpu_map *map); > >> > LIBPERF_API struct perf_cpu perf_cpu_map__cpu(const struct perf_cpu_map *cpus, int idx); > >> > LIBPERF_API int perf_cpu_map__nr(const struct perf_cpu_map *cpus); > >> > -- > >> > 2.35.1.1021.g381101b075-goog > >> > >> -- > >> > >> - Arnaldo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-28 21:25 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 6:24 [PATCH 0/5] Make evlist CPUs more accurate Ian Rogers 2022-03-28 6:24 ` Ian Rogers 2022-03-28 6:24 ` [PATCH 1/5] perf evlist: Rename cpus to user_cpus Ian Rogers 2022-03-28 6:24 ` Ian Rogers 2022-03-28 20:18 ` Arnaldo Carvalho de Melo 2022-03-28 20:18 ` Arnaldo Carvalho de Melo 2022-03-28 20:58 ` Ian Rogers 2022-03-28 20:58 ` Ian Rogers 2022-03-28 6:24 ` [PATCH 2/5] perf cpumap: More cpu map reuse by merge Ian Rogers 2022-03-28 6:24 ` Ian Rogers 2022-03-28 20:26 ` Arnaldo Carvalho de Melo 2022-03-28 20:26 ` Arnaldo Carvalho de Melo 2022-03-28 20:50 ` Ian Rogers 2022-03-28 20:50 ` Ian Rogers 2022-03-28 20:56 ` Arnaldo Carvalho de Melo 2022-03-28 20:56 ` Arnaldo Carvalho de Melo 2022-03-28 6:24 ` [PATCH 3/5] perf cpumap: Add intersect function Ian Rogers 2022-03-28 6:24 ` Ian Rogers 2022-03-28 20:28 ` Arnaldo Carvalho de Melo 2022-03-28 20:28 ` Arnaldo Carvalho de Melo 2022-03-28 20:54 ` Ian Rogers 2022-03-28 20:54 ` Ian Rogers 2022-03-28 20:59 ` Arnaldo Carvalho de Melo 2022-03-28 20:59 ` Arnaldo Carvalho de Melo 2022-03-28 21:25 ` Ian Rogers [this message] 2022-03-28 21:25 ` Ian Rogers 2022-03-28 6:24 ` [PATCH 4/5] perf stat: Avoid segv if core.user_cpus isn't set Ian Rogers 2022-03-28 6:24 ` Ian Rogers 2022-03-28 20:32 ` Arnaldo Carvalho de Melo 2022-03-28 20:32 ` Arnaldo Carvalho de Melo 2022-03-28 20:46 ` Ian Rogers 2022-03-28 20:46 ` Ian Rogers 2022-03-28 6:24 ` [PATCH 5/5] perf evlist: Respect all_cpus when setting user_cpus Ian Rogers 2022-03-28 6:24 ` 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='CAP-5=fV+DiB=_+R+g+FLgLOyY5q205OGjfsaZntVKFy4jM4rcg@mail.gmail.com' \ --to=irogers@google.com \ --cc=acme@kernel.org \ --cc=adrian.hunter@intel.com \ --cc=ak@linux.intel.com \ --cc=alexander.antonov@linux.intel.com \ --cc=alexander.shishkin@linux.intel.com \ --cc=alexey.v.bayduraev@linux.intel.com \ --cc=andrii@kernel.org \ --cc=arnaldo.melo@gmail.com \ --cc=ast@kernel.org \ --cc=bpf@vger.kernel.org \ --cc=coresight@lists.linaro.org \ --cc=daniel@iogearbox.net \ --cc=eranian@google.com \ --cc=german.gomez@arm.com \ --cc=james.clark@arm.com \ --cc=john.fastabend@gmail.com \ --cc=john.garry@huawei.com \ --cc=jolsa@kernel.org \ --cc=kafai@fb.com \ --cc=kjain@linux.ibm.com \ --cc=kpsingh@kernel.org \ --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=mark.rutland@arm.com \ --cc=mathieu.poirier@linaro.org \ --cc=mike.leach@linaro.org \ --cc=mingo@redhat.com \ --cc=namhyung@kernel.org \ --cc=netdev@vger.kernel.org \ --cc=peterz@infradead.org \ --cc=rickyman7@gmail.com \ --cc=songliubraving@fb.com \ --cc=suzuki.poulose@arm.com \ --cc=will@kernel.org \ --cc=yhs@fb.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.