From: Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
To: Paul Jackson <pj@engr.sgi.com>
Cc: Erich Focht <focht@ess.nec.de>, Robert Love <rml@tech9.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Matthew Dobson <colpatch@us.ibm.com>,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: [PATCH] O(1) scheduler set_cpus_allowed for non-current tasks
Date: Wed, 20 Feb 2002 17:40:56 -0800 [thread overview]
Message-ID: <20020220173242.2BDF.K-SUGANUMA@mvj.biglobe.ne.jp> (raw)
In-Reply-To: <Pine.SGI.4.21.0202201619560.565754-100000@sam.engr.sgi.com>
In-Reply-To: <Pine.LNX.4.21.0202202337320.10032-100000@sx6.ess.nec.de> <Pine.SGI.4.21.0202201619560.565754-100000@sam.engr.sgi.com>
Hi all,
On Wed, 20 Feb 2002 17:12:21 -0800
Paul Jackson <pj@engr.sgi.com> wrote:
> > Another problem is the right moment to change the cpu field of the
> > task. ... The IPI to the target CPU is the same as in the
> > initial design of Ingo. It has to wait for the task to unschedule and
> > knows it will find it dequeued.
>
> How about not changing anything of the target task synchronously,
> except for some new "proposed_cpus_allowed" field. Set that
> field and get out of there. Let the target process run the
> set_cpus_allowed() routine on itself, next time it passes through
> the schedule() code. Leave it the case that the set_cpus_allowed()
> routine can only be run on the current process.
>
> Perhaps others need this cpus_allowed change (and the migration
> of a task to a different allowed cpu) to happen "right away".
> But I don't, and I don't (yet) know that anyone else does.
CPU hotplug needs to change cpus_allowed in definite time.
When a process is sleeping for 100000 seconds, how can we offline
a CPU the process belongs?
Regards,
Kimi
--
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
next prev parent reply other threads:[~2002-02-21 1:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 17:57 Erich Focht
2002-02-20 19:44 ` Robert Love
2002-02-20 20:38 ` [Lse-tech] " Paul Jackson
2002-02-21 0:07 ` Erich Focht
2002-02-21 1:12 ` Paul Jackson
2002-02-21 14:38 ` Erich Focht
2002-02-21 16:59 ` Ingo Molnar
2002-02-21 15:15 ` Erich Focht
2002-02-21 21:05 ` Paul Jackson
2002-02-23 2:47 ` [Lse-tech] " Rusty Russell
2002-02-25 12:28 ` Dipankar Sarma
2002-02-26 3:59 ` Paul Jackson
2002-02-27 1:40 ` Rusty Russell
2002-02-21 1:40 ` Kimio Suganuma [this message]
2002-02-21 2:04 ` Paul Jackson
2002-02-21 4:56 ` Reid Hekman
2002-02-21 2:29 ` Kimio Suganuma
2002-02-25 20:01 ` Bill Davidsen
2002-02-21 4:49 ` [Lse-tech] " kravetz
2002-02-21 16:32 ` Ingo Molnar
2002-02-21 21:25 ` Paul Jackson
2002-02-22 9:12 ` Ingo Molnar
2002-02-22 19:44 ` [Lse-tech] " Paul Jackson
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=20020220173242.2BDF.K-SUGANUMA@mvj.biglobe.ne.jp \
--to=k-suganuma@mvj.biglobe.ne.jp \
--cc=colpatch@us.ibm.com \
--cc=focht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=pj@engr.sgi.com \
--cc=rml@tech9.net \
/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
all inboxes | Powered by JetHome®