linux-kernel - Re: [RFC] cpuset: Explicit dynamic sched domain cpuset flag

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]

Message-ID: <20061108182319.GA7924@in.ibm.com>
Date:	Wed, 8 Nov 2006 23:53:19 +0530
From:	Dinakar Guniguntala <dino@...ibm.com>
To:	Paul Jackson <pj@....com>
Cc:	nickpiggin@...oo.com.au, akpm@...l.org, mbligh@...gle.com,
	menage@...gle.com, Simon.Derr@...l.net,
	linux-kernel@...r.kernel.org, rohitseth@...gle.com, holt@....com,
	dipankar@...ibm.com, suresh.b.siddha@...el.com
Subject: Re: [RFC] cpuset:  Explicit dynamic sched domain cpuset flag

On Wed, Nov 08, 2006 at 02:38:36AM -0800, Paul Jackson wrote:
> Dinakar,
> 
> Where do we stand on this patch?
> 
> Last I knew, as of a week ago:
> 
>   * I had (still have) a patch in *-mm to nuke the old connection
>     between the cpu_exclusive flag and sched domain partitioning:
> 	cpuset-remove-sched-domain-hooks-from-cpusets.patch
>   * and you have this patch posted on lkml, with some non-trivial
>     comments from myself, to provide a new 'sched_domain' per-cpuset
>     flag to control sched domain partitioning.
> 
> Ideally, we'd agree on this new 'sched_domain' (or whatever we call it)
> flag, so that my patch to remove the old hooks could travel to 2.6.20
> along with this present patch to provide new and improved hooks.
> 
> However ... I need to focus on some other stuff for roughly four
> weeks, so can't focus on pushing this effort along right now.
> 
> My guess is that I will end up asking Andrew to hold the above
> named "remove ... hooks" patch in *-mm until you and I get our
> act together on the replacement, which most likely will mean he
> holds it until we start work on what will become 2.6.21.
> 
> Do you see any better choices?

Paul, I got busy on my end too and hope to work on it next week.
I guess I'll work on it with your suggestions and post it as soon
as I can. You can take a look at them when you are free.
Thank you for the patience

	-Dinakar
-
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/