linux-kernel - Re: [git pull] scheduler fixes

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: <20090116204049.f4d6ef1c.akpm@linux-foundation.org>
Date:	Fri, 16 Jan 2009 20:40:49 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Ingo Molnar <mingo@...e.hu>, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] scheduler fixes

On Wed, 14 Jan 2009 21:24:07 +0100 Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> On Wed, 2009-01-14 at 12:15 -0800, Andrew Morton wrote:
> > On Sun, 11 Jan 2009 15:43:05 +0100
> > Ingo Molnar <mingo@...e.hu> wrote:
> > 
> > > Please pull the latest sched-fixes-for-linus git tree
> > 
> > In http://bugzilla.kernel.org/show_bug.cgi?id=12309 the reporters have
> > identified what appears to be a sched-related performance regression. 
> > A fairly long-term one - post-2.6.18, perhaps.
> > 
> > Testcase code has been added today.  Could someone please take a look
> > sometime?
> 
> There appear to be two different bug reports in there. One about iowait,
> and one I'm not quite sure what it is about.
> 
> The second thing shows some numbers and a test case, but I fail to see
> what the problem is with it.

I had no problem seeing the problem: a gigantic performance regression
in two CPU-scheduler intensive workloads.

I can see some other problems, too.
--
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/