From: tip-bot for Ramkumar Ramachandra <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, acme@redhat.com,
hpa@zytor.com, mingo@kernel.org, jolsa@redhat.com,
dsahern@gmail.com, tglx@linutronix.de, artagnon@gmail.com
Subject: [tip:perf/urgent] perf bench: Set more defaults in the 'numa' suite
Date: Mon, 14 Apr 2014 07:54:04 -0700 [thread overview]
Message-ID: <tip-40ba93e3aa001246110320edbe8cf2eb488c1fe7@git.kernel.org> (raw)
In-Reply-To: <1395964219-22173-2-git-send-email-artagnon@gmail.com>
Commit-ID: 40ba93e3aa001246110320edbe8cf2eb488c1fe7
Gitweb: http://git.kernel.org/tip/40ba93e3aa001246110320edbe8cf2eb488c1fe7
Author: Ramkumar Ramachandra <artagnon@gmail.com>
AuthorDate: Thu, 27 Mar 2014 19:50:17 -0400
Committer: Jiri Olsa <jolsa@redhat.com>
CommitDate: Mon, 14 Apr 2014 12:55:58 +0200
perf bench: Set more defaults in the 'numa' suite
Currently,
$ perf bench numa mem
errors out with usage information. To make this more user-friendly, let
us provide a minimum set of default values required for a test
run. As an added bonus,
$ perf bench all
now goes all the way to completion.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: David Ahern <dsahern@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Link: http://lkml.kernel.org/r/1395964219-22173-2-git-send-email-artagnon@gmail.com
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
---
tools/perf/bench/numa.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/perf/bench/numa.c b/tools/perf/bench/numa.c
index d4c83c6..20697fb 100644
--- a/tools/perf/bench/numa.c
+++ b/tools/perf/bench/numa.c
@@ -1593,6 +1593,10 @@ static void init_params(struct params *p, const char *name, int argc, const char
p->data_rand_walk = true;
p->nr_loops = -1;
p->init_random = true;
+ p->mb_global_str = "1";
+ p->nr_proc = 1;
+ p->nr_threads = 1;
+ p->nr_secs = 5;
}
static int run_bench_numa(const char *name, const char **argv)
next prev parent reply other threads:[~2014-04-14 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 23:50 [PATCH 0/3] Minor fixes around perf bench Ramkumar Ramachandra
2014-03-27 23:50 ` [PATCH 1/3] perf bench: Set more defaults in the 'numa' suite Ramkumar Ramachandra
2014-04-09 12:16 ` Jiri Olsa
2014-04-11 0:31 ` Ramkumar Ramachandra
2014-04-11 10:33 ` Jiri Olsa
2014-04-14 14:54 ` tip-bot for Ramkumar Ramachandra [this message]
2014-03-27 23:50 ` [PATCH 2/3] perf bench: Update manpage to mention numa and futex Ramkumar Ramachandra
2014-04-14 14:53 ` [tip:perf/urgent] " tip-bot for Ramkumar Ramachandra
2014-03-27 23:50 ` [PATCH 3/3] perf bench: Fix segfault at the end of an 'all' execution Ramkumar Ramachandra
2014-04-14 14:53 ` [tip:perf/urgent] " tip-bot for Ramkumar Ramachandra
2014-03-27 23:57 ` [PATCH 0/3] Minor fixes around perf bench Davidlohr Bueso
2014-04-06 14:23 ` Jiri Olsa
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=tip-40ba93e3aa001246110320edbe8cf2eb488c1fe7@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=artagnon@gmail.com \
--cc=dsahern@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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