From: Andi Kleen <ak@linux.intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Alexey Budankov <alexey.budankov@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Kan Liang <kan.liang@intel.com>,
Dmitri Prokhorov <Dmitry.Prohorov@intel.com>,
Valery Cherepennikov <valery.cherepennikov@intel.com>,
David Carrillo-Cisneros <davidcc@google.com>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/n] perf/core: addressing 4x slowdown during per-process profiling of STREAM benchmark on Intel Xeon Phi
Date: Mon, 19 Jun 2017 08:21:51 -0700 [thread overview]
Message-ID: <20170619152151.GB23705@tassilo.jf.intel.com> (raw)
In-Reply-To: <20170619150939.GA4555@leverpostej>
> I was trying to get a feel for how that compares to what we can do
> today. For other reasons (e.g. fd exhaustion), opening NR_CPUS * n
You just have to increase the fd limit. The 1024 fd default is just
archaic for larger systems and doesn't really make any sense because
it only controls very small amounts of kernel memory.
> events might not be a great idea on systems with a huge number of CPUs.
> We might want a heuristic in the perf tool regardless.
But there's no alternative: we have to measure all CPUs with all events.
-andi
next prev parent reply other threads:[~2017-06-19 15:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 17:41 [PATCH v3 1/n] perf/core: addressing 4x slowdown during per-process profiling of STREAM benchmark on Intel Xeon Phi Alexey Budankov
2017-06-15 19:56 ` Mark Rutland
2017-06-15 22:10 ` Alexey Budankov
2017-06-16 9:09 ` Mark Rutland
2017-06-16 14:08 ` Alexey Budankov
2017-06-16 14:22 ` Alexey Budankov
2017-06-19 12:46 ` Mark Rutland
2017-06-19 13:38 ` Mark Rutland
2017-06-19 14:09 ` Alexey Budankov
2017-06-19 14:59 ` Andi Kleen
2017-06-19 15:09 ` Mark Rutland
2017-06-19 15:21 ` Andi Kleen [this message]
2017-06-19 15:24 ` Mark Rutland
2017-06-19 15:39 ` Andi Kleen
2017-06-19 15:52 ` Mark Rutland
2017-06-19 13:08 ` Alexey Budankov
2017-06-19 13:26 ` Mark Rutland
2017-06-19 13:37 ` Alexey Budankov
2017-06-19 15:00 ` Alexey Budankov
2017-06-19 15:24 ` Andi Kleen
2017-06-19 15:34 ` Alexey Budankov
2017-06-30 10:23 ` Alexey Budankov
2017-06-30 10:21 ` Alexey Budankov
2017-06-19 15:14 ` Mark Rutland
2017-06-19 15:27 ` Alexey Budankov
2017-06-30 10:21 ` Alexey Budankov
2017-06-19 20:31 ` Alexey Budankov
2017-06-20 13:36 ` Mark Rutland
2017-06-20 15:22 ` Alexey Budankov
2017-06-20 16:37 ` Mark Rutland
2017-06-20 17:10 ` Alexey Budankov
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=20170619152151.GB23705@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=Dmitry.Prohorov@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valery.cherepennikov@intel.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