From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [REGRESSION] funny sched_domain build failure during resume
Date: Fri, 9 May 2014 18:15:45 +0200 [thread overview]
Message-ID: <20140509161545.GX30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140509160455.GA4486@htj.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Fri, May 09, 2014 at 12:04:55PM -0400, Tejun Heo wrote:
> It looks like the allocation is for a temp buffer and there are also
> percpu allocations going on. Maybe just allocate the buffers on boot
> and keep them around?
Its not a scratch buffer, but we could certainly try and keep it around
over suspend/resume.
I'll try and prod at that on monday.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-09 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 16:04 [REGRESSION] funny sched_domain build failure during resume Tejun Heo
2014-05-09 16:15 ` Peter Zijlstra [this message]
2014-05-14 14:00 ` Peter Zijlstra
2014-05-14 14:05 ` Peter Zijlstra
2014-05-14 17:02 ` Tejun Heo
2014-05-14 17:10 ` Peter Zijlstra
2014-05-14 22:36 ` Tejun Heo
2014-05-15 8:57 ` Peter Zijlstra
2014-05-15 14:41 ` Johannes Weiner
2014-05-15 15:12 ` Peter Zijlstra
2014-05-16 11:47 ` Srivatsa S. Bhat
2014-05-15 8:40 ` Juri Lelli
2014-05-15 8:51 ` Peter Zijlstra
2014-05-15 11:52 ` Juri Lelli
2014-05-16 10:43 ` Peter Zijlstra
2014-05-16 11:01 ` Juri Lelli
2014-05-16 11:04 ` Peter Zijlstra
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=20140509161545.GX30445@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tj@kernel.org \
/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