From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "he, bo" <bo.he@intel.com>
Cc: akpm@linux-foundation.org, mingo@elte.hu, rusty@rustcorp.com.au,
william.douglas@intel.com, linux-kernel@vger.kernel.org,
yanmin_zhang@linux.intel.com, yanmin.zhang@intel.com
Subject: Re: [PATCH] sched: fix OOPS when build_sched_domains percpu allocation fails
Date: Wed, 25 Apr 2012 14:20:27 +0200 [thread overview]
Message-ID: <1335356427.28150.264.camel@twins> (raw)
In-Reply-To: <1335355161.5892.17.camel@hebo>
On Wed, 2012-04-25 at 19:59 +0800, he, bo wrote:
> From: "he, bo" <bo.he@intel.com>
>
> Under extreme memory used up situation, percpu allocation
> might fails. We hit it when system go to suspend-to-ram.
Thanks!
next prev parent reply other threads:[~2012-04-25 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 11:59 [PATCH] sched: fix OOPS when build_sched_domains percpu allocation fails he, bo
2012-04-25 12:20 ` Peter Zijlstra [this message]
2012-04-25 12:59 ` Srivatsa S. Bhat
2012-04-26 11:56 ` [tip:sched/urgent] sched: Fix OOPS when build_sched_domains() " tip-bot for he, bo
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=1335356427.28150.264.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bo.he@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=william.douglas@intel.com \
--cc=yanmin.zhang@intel.com \
--cc=yanmin_zhang@linux.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