All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Nathan Lynch <ntl@pobox.com>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	lkml <linux-kernel@vger.kernel.org>,
	ACPI List <acpi-devel@lists.sourceforge.net>,
	Zwane Mwaikambo <zwane@linuxpower.ca>,
	"Brown, Len" <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 15:56:48 -0700	[thread overview]
Message-ID: <20050404155647.A8944@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050404224620.GD3611@otto>; from ntl@pobox.com on Mon, Apr 04, 2005 at 03:46:20PM -0700

On Mon, Apr 04, 2005 at 03:46:20PM -0700, Nathan Lynch wrote:
> 
>    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
> 
>    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.
> 

In ia64 we create idle threads on demand if one is not available for the same
logical cpu number, and re-used when the same logical cpu number is re-used. 

just a minor improvement, i also thought about idle exit, but wasnt worth
anything in return.

Cheers,
ashok

  parent reply	other threads:[~2005-04-04 22:56 UTC|newest]

Thread overview: 22+ 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  2:07 ` Li Shaohua
     [not found] ` <1112580367.4194.344.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04  5:28   ` Nathan Lynch
2005-04-04  5:28     ` Nathan Lynch
2005-04-04  5:42     ` Li Shaohua
2005-04-04  5:42       ` [ACPI] " Li Shaohua
     [not found]       ` <1112593338.4194.362.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04 15:33         ` Nathan Lynch
2005-04-04 15:33           ` [ACPI] " Nathan Lynch
2005-04-04 22:14           ` Nigel Cunningham
2005-04-04 22:14             ` [ACPI] " Nigel Cunningham
     [not found]             ` <1112652864.3757.31.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-04-04 22:46               ` Nathan Lynch
2005-04-04 22:46                 ` [ACPI] " Nathan Lynch
2005-04-04 22:56                 ` Nigel Cunningham
2005-04-04 22:56                 ` Ashok Raj [this message]
2005-04-05  1:55           ` Li Shaohua
     [not found]             ` <1112666106.17861.62.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-06  4:28               ` Nathan Lynch
2005-04-06  4:28                 ` [ACPI] " Nathan Lynch
2005-04-05  9:00           ` Li Shaohua
2005-04-05  9:00             ` [ACPI] " Li Shaohua
2005-04-04 19:11   ` Zwane Mwaikambo
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=20050404155647.A8944@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --cc=ntl@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.