linux-kernel - Re: [PATCH 0/2] prefer wakers -v2

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: <1232116075.6141.29.camel@marge.simson.net>
Date:	Fri, 16 Jan 2009 15:27:55 +0100
From:	Mike Galbraith <efault@....de>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] prefer wakers -v2

On Wed, 2009-01-14 at 12:39 +0100, Peter Zijlstra wrote:
> OK, so lets try this again...

I took tip out for a little test-drive.  Mysql/pgsql+oltp showed no
effect vs 29.git beyond noise level, but cache hot make -j8 kbuild times
in an nfs4 mount show marked improvement.

2.6.29.git
real    6m29.291s
user    10m20.355s
sys     2m1.288s

2.6.29.tip
real    4m30.160s
user    10m26.115s
sys     2m3.088s

Wire saturates at ~4m, so there's still some room for improvement.

On the interactivity front, tip feels snappier, particularly when IO is
going on.  One place that this is quite noticeable is reading lkml with
evolution while building a new kernel.  I generally keep thread count
low when using evolution because IO makes it sluggish when deleting and
moving on to the next message.  With tip, the evolution experience is
much improved.

	-Mike

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