linux-kernel - Re: [RFC][PATCH 1/2] sched: higher granularity load on 64bit systems

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] [day] [month] [year] [list]

Message-Id: <1209019640.7115.345.camel@twins>
Date:	Thu, 24 Apr 2008 08:47:20 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	David Miller <davem@...emloft.net>
Cc:	mingo@...e.hu, dhaval@...ux.vnet.ibm.com, vatsa@...ibm.com,
	dmitry.adamushko@...il.com, linux-kernel@...r.kernel.org,
	efault@....de
Subject: Re: [RFC][PATCH 1/2] sched: higher granularity load on 64bit
	systems

On Wed, 2008-04-23 at 17:27 -0700, David Miller wrote:
> From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Date: Thu, 24 Apr 2008 00:07:56 +0200
> 
> > The below is an RFC because for some reason it regresses kbuild by 5% on
> > my machine (and more on the largesmp that are the reason for it).
> 
> This causes my 64-cpu Niagara2 box to completely hang when I run "make
> clean" on a kernel tree after a fresh bootup.
> 
> Can we just revert all of this broken code until it's sorted out? :-/
> 
> We're going on 4 days with unfixed major regressions from the
> scheduler tree merge, and these regressions make systems unusable.
> 
> This is blocking my own work, and I'm starting to lose my patience.

Yes, this is all rather embarassing - if you want a revert of the
offending patches I can spin you one, and if this isn't solved quickly
I'm afraid we'll indeed have to revert in -linus :-/

Sorry about this.

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