linux-kernel - Re: [RFC, PATCH 0/5] Going forward with Resource Management

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: <20060803224253.49068b98.akpm@osdl.org>
Date:	Thu, 3 Aug 2006 22:42:53 -0700
From:	Andrew Morton <akpm@...l.org>
To:	vatsa@...ibm.com, mingo@...e.hu, nickpiggin@...oo.com.au,
	sam@...ain.net, linux-kernel@...r.kernel.org, dev@...nvz.org,
	efault@....de, balbir@...ibm.com, sekharan@...ibm.com,
	nagar@...son.ibm.com, haveblue@...ibm.com, pj@....com
Subject: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu
 controller

On Thu, 3 Aug 2006 22:36:50 -0700
Andrew Morton <akpm@...l.org> wrote:

> I thought the most recently posted CKRM core was a fine piece of code.

I mean, subject to more review, testing, input from stakeholders and blah,
I'd be OK with merging the CKRM core fairly aggressively.  With just a
minimal controller suite.  Because it is good to define the infrastructure
and APIs for task grouping and to then let the controllers fall into place.

The downside to such a strategy is that there is a risk that nobody ever
gets around to implementing useful controllers, so it ends up dead code. 
I'd judge that the interest in resource management is such that the risk of
this happening is low.

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