linux-kernel - Re: [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomainmanagment (take 2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Jul 2008 13:46:58 -0600
From:	"Gregory Haskins" <ghaskins@...ell.com>
To:	"Max Krasnyansky" <maxk@...lcomm.com>
Cc:	<a.p.zijlstra@...llo.nl>, <mingo@...e.hu>,
	<dmitry.adamushko@...il.com>, <torvalds@...ux-foundation.org>,
	<pj@....com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpu hotplug, sched:
	Introduce	cpu_active_map	and	redoscheddomainmanagment (take 2)

>>> On Thu, Jul 17, 2008 at  2:52 PM, in message <487F9509.9050802@...lcomm.com>,
Max Krasnyansky <maxk@...lcomm.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/