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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1232182351.7141.37.camel@twins>
Date:	Sat, 17 Jan 2009 09:52:31 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] scheduler fixes

On Fri, 2009-01-16 at 20:40 -0800, Andrew Morton wrote:
> 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.

Right, but it wasn't clearly stated what the issue was, and there seem
to be two with that testcase

 1) the total running time increases
 2) it causes some severe latency spikes

Now why it was stuck in with that iowait thing I have no clue, as it
doesn't do anything with iowait, I ran the thing (well, both things) and
iowait is 0%.

Of course we'll try and fix these issues -- but as far as I'm concerned
its utterly unrelated to the iowait thing.

> I can see some other problems, too.

The universe is full of problems, mixing them all up doesn't get us
anywhere.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ