public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Simon Derr <Simon.Derr@bull.net>,
	Nicolas Capit <nicolas.capit@imag.fr>,
	linux-kernel@vger.kernel.org, Paul Jackson <pj@sgi.com>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	Paul Menage <menage@google.com>, Balbir Singh <balbir@in.ibm.com>
Subject: Re: cpuset trouble after hibernate
Date: Mon, 17 Sep 2007 23:41:37 +0530	[thread overview]
Message-ID: <46EEC359.8070508@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070915010807.b0055e7e.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Mon, 10 Sep 2007 11:45:10 +0200 (CEST) Simon Derr <Simon.Derr@bull.net> wrote:
> 
>> On Sat, 8 Sep 2007, Nicolas Capit wrote:
>>
>>> Hello,
>>>
>>> This is my situation:
>>>   - I mounted the pseudo cpuset filesystem into /dev/cpuset
>>>   - I created a cpuset named oar with my 2 cpus
>>>
>>> cat /dev/cpuset/oar/cpus 
>>> 0-1
>>>
>>>   - Then I hibernate my computer with 'echo -n "disk" >/sys/power/state'
>>>   - After reboot:
>>>
>>> cat /dev/cpuset/oar/cpus 
>>> 0
>>>
>>> Why did I lost a cpu?
>>> Is this a normal behavior???
>> Hi Nicolas,
>>
>> I believe this is related to the fact that hibernation uses the hotplug 
>> subsystem to disable all CPUs except the boot CPU.
>>
>> Thus guarantee_online_cpus() is called on each cpuset and removes all 
>> CPUs, except CPU 0, from all cpusets.
>>
>> I'm not quite sure about if/how this should be fixed in the kernel, 
>> though. Looks like a very simple user-land workaround would be enough.
>>
> 
> Yeah.  Bug, surely.  But I guess it's always been there.
> 
> What are the implications of this for cpusets-via-containers?
> 

I suspect the functionality of cpusets is not affected by containers.

I wonder if containers should become suspend/resume aware and pass
that option on to controllers. I think it's only the bus drivers
and device drivers that do that now.



-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

      parent reply	other threads:[~2007-09-17 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 18:44 cpuset trouble after hibernate Nicolas Capit
2007-09-09 11:18 ` Pavel Machek
2007-09-19  0:59   ` Paul Menage
2007-09-10  9:45 ` Simon Derr
2007-09-10  9:55   ` Nicolas Capit
2007-09-15  8:08   ` Andrew Morton
2007-09-17 18:04     ` Paul Menage
2007-09-17 18:11     ` Balbir Singh [this message]

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=46EEC359.8070508@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=nicolas.capit@imag.fr \
    --cc=pj@sgi.com \
    --cc=serue@us.ibm.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