linux-kernel - Re: [RFC] Reverting NUMA-affine page table allocation

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:	Wed, 2 Mar 2011 19:31:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Reverting NUMA-affine page table allocation


* Tejun Heo <tj@...nel.org> wrote:

> On Wed, Mar 02, 2011 at 07:19:41PM +0100, Ingo Molnar wrote:
> > Hm, i thought the revert was for tip:x86/mm, not x86/urgent. The development window 
> > for 2.6.39 is closing down.
> > 
> > A revert (without an actual bug that it fixes) for -rc8 is definitely out of 
> > question.
> 
> It is for x86/mm and it does address the unnecessarily smaller mapping
> problem, which Yinghai's further patches address too.  Those patches
> are what triggered me to ask for a revert because they kinda show how
> ugly the underlying code is and add on top of it.

Yeah - i agree with you and hpa that deferring this to .40 is the most sensible 
approach.

The splitting up into small regions side-effect was rather nasty to begin with - it 
would have taken who knows how many cycles for someone to notice that based on raw 
analysis of the pagetables ...

We need to slow down here for .39.

Thanks,

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