From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org,
davem@davemloft.net, perfmon2-devel@lists.sf.net,
eranian@gmail.com, robert.richter@amd.com,
"markus.t.metzger" <markus.t.metzger@intel.com>
Subject: Re: [PATCH] perf_events: improve DS/BTS/PEBS buffer allocation
Date: Mon, 13 Sep 2010 20:57:52 +0200 [thread overview]
Message-ID: <1284404272.2275.419.camel@laptop> (raw)
In-Reply-To: <AANLkTimsp5NphG3VuwO_FoWZhjF8crD3=bKhXDq-_wyn@mail.gmail.com>
On Mon, 2010-09-13 at 20:49 +0200, Stephane Eranian wrote:
> On Mon, Sep 13, 2010 at 8:42 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Mon, 2010-09-13 at 20:40 +0200, Stephane Eranian wrote:
> >> Ok, so can we play the same trick you're playing with the sampling
> >> buffer, i.e., you use alloc_pages_node() for one page at a time, and
> >> then you stitch them on demand via SW?
> >
> > Not for BTS, it wants a linear range, getting the vmalloc vs NMI thing
> > sorted would be best I think.
> >
> What is annoying in this is that you run into the problem even though
> you may not be using BTS nor PEBS.
Yes, one thing we could do is simply disable BTS when we fail that
alloc, instead of fail everything.
> What mitigates the problem, I think, is the NMI watchdog. It is the first
> user of perf_events. As such, the BTS and PEBS buffers get allocated
> during kernel initialization thereby increasing the chances of finding
> contiguous chunks of memory. What would partly help would be to use of
> kmalloc_node() to at least balance allocations amongst the various NUMA
> nodes. That would be until the vmalloc() vs. NMI is sorted out.
Right, that would be a simple change to make.
next prev parent reply other threads:[~2010-09-13 18:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 14:55 [PATCH] perf_events: improve DS/BTS/PEBS buffer allocation Stephane Eranian
2010-09-13 15:08 ` Peter Zijlstra
2010-09-13 15:21 ` Stephane Eranian
2010-09-13 15:09 ` Frederic Weisbecker
2010-09-13 15:13 ` Stephane Eranian
2010-09-13 15:16 ` Peter Zijlstra
2010-09-13 15:20 ` Stephane Eranian
2010-09-13 15:24 ` Peter Zijlstra
2010-09-13 15:31 ` Stephane Eranian
2010-09-13 15:41 ` Peter Zijlstra
2010-09-13 15:51 ` Frederic Weisbecker
2010-09-13 15:55 ` Stephane Eranian
2010-09-13 17:35 ` Peter Zijlstra
2010-09-13 18:40 ` Stephane Eranian
2010-09-13 18:42 ` Peter Zijlstra
2010-09-13 18:49 ` Stephane Eranian
2010-09-13 18:57 ` Peter Zijlstra [this message]
2010-09-13 19:12 ` Stephane Eranian
2010-09-13 19:31 ` Mathieu Desnoyers
2010-09-13 19:34 ` Peter Zijlstra
2010-09-13 19:35 ` Peter Zijlstra
2010-09-13 19:42 ` Mathieu Desnoyers
2010-09-13 17:24 ` Stephane Eranian
2010-09-13 17:36 ` Peter Zijlstra
2010-09-13 19:35 ` Andi Kleen
2010-09-13 19:49 ` Peter Zijlstra
2010-09-13 20:51 ` Andi Kleen
2010-09-13 20:57 ` [perfmon2] " Luck, Tony
2010-09-13 20:34 ` H. Peter Anvin
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=1284404272.2275.419.camel@laptop \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=robert.richter@amd.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