From: "Gregory Haskins" <ghaskins@novell.com>
To: "Max Krasnyansky" <maxk@qualcomm.com>
Cc: <a.p.zijlstra@chello.nl>, <mingo@elte.hu>,
<dmitry.adamushko@gmail.com>, <torvalds@linux-foundation.org>,
<pj@sgi.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomainmanagment (take 2)
Date: Thu, 17 Jul 2008 13:46:58 -0600 [thread overview]
Message-ID: <487F6972.BA47.005A.0@novell.com> (raw)
In-Reply-To: <487F9509.9050802@qualcomm.com>
>>> On Thu, Jul 17, 2008 at 2:52 PM, in message <487F9509.9050802@qualcomm.com>,
Max Krasnyansky <maxk@qualcomm.com> wrote:
> Gregory Haskins wrote:
>>
>> Hi Max,
>> Thanks for the pointers. I see that I did indeed misunderstand the intent
>> of the patch. It seems you already solved the rebuild problem, and were
>> just trying to solve the "migrate to a dead cpu" problem that Linus mentions
>> as a solution with cpu_active_map.
>
> Yes. btw they are definitely related, because the reason we were blowing
> away the domains is to avoid "migration to a dead cpu". ie We were relying
> on the fact that domain masks never contain cpus that are either dying or
> already dead.
Agreed.
>>
>> Thoughts?
>
> None at this point :). I need to run right now and will try to look at this
> later today. My knowledge of the internal sched structs is definitely
> lacking so I need to look at the rq->rd thing to have and opinion.
Sounds good, Max. Thanks!
-Greg
next prev parent reply other threads:[~2008-07-17 19:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 11:43 [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redo sched domain managment (take 2) Max Krasnyansky
2008-07-15 11:49 ` Marcel Holtmann
2008-07-15 11:52 ` Peter Zijlstra
2008-07-15 11:57 ` Marcel Holtmann
2008-07-15 12:03 ` Peter Zijlstra
2008-07-15 15:24 ` Linus Torvalds
2008-07-15 12:45 ` Gregory Haskins
2008-07-15 15:22 ` Linus Torvalds
2008-07-16 8:57 ` Dmitry Adamushko
2008-07-16 20:29 ` Max Krasnyansky
2008-07-16 21:55 ` Dmitry Adamushko
2008-07-16 12:12 ` Gregory Haskins
2008-07-16 21:44 ` Max Krasnyansky
2008-07-17 2:51 ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redosched " Gregory Haskins
2008-07-17 7:16 ` Max Krasnyansky
2008-07-17 11:57 ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomain " Gregory Haskins
2008-07-17 18:52 ` Max Krasnyansky
2008-07-17 19:46 ` Gregory Haskins [this message]
2008-07-18 11:53 ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomainmanagment " Peter Zijlstra
2008-07-18 12:22 ` [PATCH] cpu hotplug, sched:Introduce " Gregory Haskins
2008-07-22 5:10 ` Max Krasnyansky
2008-07-22 14:06 ` Gregory Haskins
2008-07-22 14:16 ` Peter Zijlstra
2008-07-22 14:17 ` Gregory Haskins
2008-07-22 14:26 ` Peter Zijlstra
2008-07-22 14:45 ` Gregory Haskins
2008-07-22 19:32 ` Max Krasnyansky
2008-08-11 13:11 ` Gregory Haskins
2008-08-11 21:57 ` Max Krasnyansky
2008-07-18 11:30 ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redo sched domain managment " Ingo Molnar
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=487F6972.BA47.005A.0@novell.com \
--to=ghaskins@novell.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=torvalds@linux-foundation.org \
/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