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: <20060804115108.04a2af70.akpm@osdl.org>
Date:	Fri, 4 Aug 2006 11:51:08 -0700
From:	Andrew Morton <akpm@...l.org>
To:	vatsa@...ibm.com
Cc:	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 Fri, 4 Aug 2006 16:46:38 +0530
Srivatsa Vaddagiri <vatsa@...ibm.com> wrote:

> On Fri, Aug 04, 2006 at 12:13:42AM -0700, Andrew Morton wrote:
> > There was a lot of discussion last time - Mike, Ingo, others.  It would be
> > a useful starting point if we could be refreshed on what the main issues
> > were, and whether/how this new patchset addresses them.
> 
> The main issues raised against the CPU controller posted last time were
> these:
> 

A useful summary, thanks.  It will probably help people if this description
could be maintained along with the patch.  Because these issues are complex
and we have a habit of dropping the ball then picking it up months later
when everyone has forgotten everything.

> 
> Ingo/Nick, what are your thoughts here?

I believe Ingo is having a bit of downtime for another week or so.
-
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/