From: Dave Hansen <dave.hansen@intel.com>
To: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"Yan, Zheng" <zheng.z.yan@intel.com>
Subject: Re: [RFC] perf/x86: PMU IRQ handler issues
Date: Wed, 28 May 2014 13:20:39 -0700 [thread overview]
Message-ID: <53864517.3040503@intel.com> (raw)
In-Reply-To: <CABPqkBTsiwicZNuU5BW6FZfB4aC=T=w9vFoxLqBTV3-PS4BnoA@mail.gmail.com>
On 05/28/2014 12:48 PM, Stephane Eranian wrote:
> Some days ago, I was alerted that under important network load, something
> is going wrong with perf_event sampling in frequency mode (such as perf top).
> The number of samples was way too low given the cycle count (via perf stat).
> Looking at the syslog, I noticed that the perf irq latency throttler
> had kicked in
> several times. There may have been several reasons for this.
>
> Maybe the workload had changing phases and the frequency adjustments
> was not working properly and dropping to very small period and then generated
> flood of interrupts.
The problem description here is pretty fuzzy. Could you give some
actual numbers describing the issues that you're seeing, including the
ftrace that Andi was asking for? There are also some handy tracepoints
for NMI lengths that I stuck in.
The reason that the throttling code is there is that the CPU can get in
to a state where it is doing *NOTHING* other than processing NMIs (the
biggest of which are the perf-driven ones). It doesn't start throttling
until 128 samples end up averaging more than the limit.
How large of a system is this, btw? I had the worst issues on a
160-logical-cpu system. It was much harder to get it to trouble on
smaller systems.
next prev parent reply other threads:[~2014-05-28 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 19:48 [RFC] perf/x86: PMU IRQ handler issues Stephane Eranian
2014-05-28 19:55 ` Andi Kleen
2014-05-28 19:56 ` Stephane Eranian
2014-05-28 20:06 ` Andi Kleen
2014-05-28 20:20 ` Dave Hansen [this message]
2014-05-29 2:56 ` Andi Kleen
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=53864517.3040503@intel.com \
--to=dave.hansen@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=zheng.z.yan@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