From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Namhyung Kim <namhyung.kim@lge.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] perf bench: Change the procps visible command-name of invididual benchmark tests
Date: Tue, 24 Sep 2013 06:39:52 -0600 [thread overview]
Message-ID: <52418818.3050308@gmail.com> (raw)
In-Reply-To: <20130924103900.GA5085@gmail.com>
On 9/24/13 4:39 AM, Ingo Molnar wrote:
> +/*
> + * Run a specific benchmark but first rename the running task's ->comm[]
> + * to something meaningful:
> + */
> +static int run_bench(const char *subsys_name, const char *bench_name, bench_fn_t fn, int argc, const char **argv, const char *prefix)
As I recall you are a fan of longer line lengths, but this seems
excessive. ;-)
---8<---
> +}
> +
> +static void all_suites(struct bench_subsys *subsys) /* FROM HERE */
Might as well drop the /* FROM HERE */.
---8<---
> @@ -244,8 +269,7 @@ int cmd_bench(int argc, const char **arg
> subsystems[i].name,
> subsystems[i].suites[j].name);
> fflush(stdout);
> - status = subsystems[i].suites[j].fn(argc - 1,
> - argv + 1, prefix);
> + status = run_bench(subsystems[i].name, subsystems[i].suites[j].name, subsystems[i].suites[j].fn, argc - 1, argv + 1, prefix);
another one that is rather long.
David
prev parent reply other threads:[~2013-09-24 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 10:39 [PATCH] perf bench: Change the procps visible command-name of invididual benchmark tests Ingo Molnar
2013-09-24 12:39 ` David Ahern [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=52418818.3050308@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.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).