From: Nathan Lynch <ntl@pobox.com>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Li Shaohua <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
ACPI List <acpi-devel@lists.sourceforge.net>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>
Subject: Re: [ACPI] Re: [RFC 5/6]clean cpu state after hotremove CPU
Date: Mon, 4 Apr 2005 17:46:20 -0500 [thread overview]
Message-ID: <20050404224620.GD3611@otto> (raw)
In-Reply-To: <1112652864.3757.31.camel@desktop.cunningham.myip.net.au>
Hi Nigel!
On Tue, Apr 05, 2005 at 08:14:25AM +1000, Nigel Cunningham wrote:
>
> On Tue, 2005-04-05 at 01:33, Nathan Lynch wrote:
> > > Yes, exactly. Someone who understand do_exit please help clean up the
> > > code. I'd like to remove the idle thread, since the smpboot code will
> > > create a new idle thread.
> >
> > I'd say fix the smpboot code so that it doesn't create new idle tasks
> > except during boot.
>
> Would that mean that CPUs that were physically hotplugged wouldn't get
> idle threads?
No, that wouldn't work. I am saying that there's little to gain by
adding all this complexity for destroying the idle tasks when it's
fairly simple to create num_possible_cpus() - 1 idle tasks* to
accommodate any additional cpus which may come along. This is what
ppc64 does now, and it should be feasible on any architecture which
supports cpu hotplug.
Nathan
* num_possible_cpus() - 1 because the idle task for the boot cpu is
created in sched_init.
next prev parent reply other threads:[~2005-04-05 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:07 [RFC 5/6]clean cpu state after hotremove CPU Li Shaohua
2005-04-04 5:28 ` Nathan Lynch
2005-04-04 5:42 ` [ACPI] " Li Shaohua
2005-04-04 15:33 ` Nathan Lynch
2005-04-04 22:14 ` Nigel Cunningham
2005-04-04 22:46 ` Nathan Lynch [this message]
2005-04-04 22:56 ` Nigel Cunningham
2005-04-04 22:56 ` Ashok Raj
2005-04-05 1:55 ` Li Shaohua
2005-04-06 4:28 ` Nathan Lynch
2005-04-05 9:00 ` Li Shaohua
2005-04-04 19:11 ` Zwane Mwaikambo
2005-04-05 1:06 ` Li Shaohua
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=20050404224620.GD3611@otto \
--to=ntl@pobox.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--cc=shaohua.li@intel.com \
--cc=zwane@linuxpower.ca \
/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