From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Song Liu <songliubraving@fb.com>,
Blake Jones <blakejones@google.com>
Subject: Re: [PATCH 2/3] perf lock: Add -m/--map-length option
Date: Tue, 2 Aug 2022 14:43:19 -0300 [thread overview]
Message-ID: <YuliN2UDbls5uW3u@kernel.org> (raw)
In-Reply-To: <20220802073511.299459-2-namhyung@kernel.org>
Em Tue, Aug 02, 2022 at 12:35:10AM -0700, Namhyung Kim escreveu:
> The -m/--map-length option is to control number of max entries in the
> perf lock contention BPF maps.
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/Documentation/perf-lock.txt | 4 ++++
> tools/perf/builtin-lock.c | 23 ++++++++++++++++++++++-
> tools/perf/util/bpf_lock_contention.c | 3 +++
> tools/perf/util/lock-contention.h | 1 +
> 4 files changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/Documentation/perf-lock.txt b/tools/perf/Documentation/perf-lock.txt
> index 7949d2e6891b..2101644785e0 100644
> --- a/tools/perf/Documentation/perf-lock.txt
> +++ b/tools/perf/Documentation/perf-lock.txt
> @@ -145,6 +145,10 @@ CONTENTION OPTIONS
> --tid=::
> Record events on existing thread ID (comma separated list).
>
> +-m::
> +--map-length::
> + Maximum number of BPF map entries (default: 10240).
--map-nr-entries?
I think we use this jargon "nr-entries" for arrays, lists, etc, better
try to stick to it.
Also what do you think about not using single letter options for things
that are not that used?
The map size has a default, one that seems generous, so changing it
should be something uncommon, and then, if it becomes common that more
entries are needed by default, we can change the default in the tool.
- Arnaldo
> +
>
> SEE ALSO
> --------
> diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> index eef778b7d33d..e32fdcd497e0 100644
> --- a/tools/perf/builtin-lock.c
> +++ b/tools/perf/builtin-lock.c
> @@ -55,6 +55,7 @@ static struct rb_root thread_stats;
> static bool combine_locks;
> static bool show_thread_stats;
> static bool use_bpf;
> +static unsigned long bpf_map_len = 10240;
>
> static enum {
> LOCK_AGGR_ADDR,
> @@ -1597,6 +1598,7 @@ static int __cmd_contention(int argc, const char **argv)
> struct lock_contention con = {
> .target = &target,
> .result = &lockhash_table[0],
> + .map_len = bpf_map_len,
> };
>
> session = perf_session__new(use_bpf ? NULL : &data, &eops);
> @@ -1786,6 +1788,24 @@ static int __cmd_record(int argc, const char **argv)
> return ret;
> }
>
> +static int parse_map_length(const struct option *opt, const char *str,
> + int unset __maybe_unused)
> +{
> + unsigned long *len = (unsigned long *)opt->value;
> + unsigned long val;
> + char *endptr;
> +
> + errno = 0;
> + val = strtoul(str, &endptr, 0);
> + if (*endptr != '\0' || errno != 0) {
> + pr_err("invalid BPF map length: %s\n", str);
> + return -1;
> + }
> +
> + *len = val;
> + return 0;
> +}
> +
> int cmd_lock(int argc, const char **argv)
> {
> const struct option lock_options[] = {
> @@ -1835,9 +1855,10 @@ int cmd_lock(int argc, const char **argv)
> "List of cpus to monitor"),
> OPT_STRING('p', "pid", &target.pid, "pid",
> "Trace on existing process id"),
> - /* TODO: Add short option -t after -t/--tracer can be removed. */
> OPT_STRING(0, "tid", &target.tid, "tid",
> "Trace on existing thread id (exclusive to --pid)"),
> + OPT_CALLBACK('m', "map-length", &bpf_map_len, "len",
> + "Max number of BPF map entries", parse_map_length),
> OPT_PARENT(lock_options)
> };
>
> diff --git a/tools/perf/util/bpf_lock_contention.c b/tools/perf/util/bpf_lock_contention.c
> index f5e2b4f19a72..26128e5bb659 100644
> --- a/tools/perf/util/bpf_lock_contention.c
> +++ b/tools/perf/util/bpf_lock_contention.c
> @@ -40,6 +40,9 @@ int lock_contention_prepare(struct lock_contention *con)
> return -1;
> }
>
> + bpf_map__set_max_entries(skel->maps.stacks, con->map_len);
> + bpf_map__set_max_entries(skel->maps.lock_stat, con->map_len);
> +
> if (target__has_cpu(target))
> ncpus = perf_cpu_map__nr(evlist->core.user_requested_cpus);
> if (target__has_task(target))
> diff --git a/tools/perf/util/lock-contention.h b/tools/perf/util/lock-contention.h
> index a0df5308cca4..b09fd6eb978a 100644
> --- a/tools/perf/util/lock-contention.h
> +++ b/tools/perf/util/lock-contention.h
> @@ -112,6 +112,7 @@ struct lock_contention {
> struct target *target;
> struct machine *machine;
> struct hlist_head *result;
> + unsigned long map_len;
> };
>
> #ifdef HAVE_BPF_SKEL
> --
> 2.37.1.455.g008518b4e5-goog
--
- Arnaldo
next prev parent reply other threads:[~2022-08-02 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:35 [PATCH 1/3] perf lock: Introduce struct lock_contention Namhyung Kim
2022-08-02 7:35 ` [PATCH 2/3] perf lock: Add -m/--map-length option Namhyung Kim
2022-08-02 17:43 ` Arnaldo Carvalho de Melo [this message]
2022-08-02 18:05 ` Namhyung Kim
2022-08-02 18:17 ` Arnaldo Carvalho de Melo
2022-08-02 7:35 ` [PATCH 3/3] perf lock: Print lost entries at the end Namhyung Kim
2022-08-02 17:45 ` Arnaldo Carvalho de Melo
2022-08-02 18:08 ` Namhyung Kim
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=YuliN2UDbls5uW3u@kernel.org \
--to=acme@kernel.org \
--cc=blakejones@google.com \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).