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: <20100913200018.GA31186@elte.hu>
Date:	Mon, 13 Sep 2010 22:00:18 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tony Lindgren <tony@...mide.com>,
	Mike Galbraith <efault@....de>
Subject: Re: [PATCH] sched: Improve latencies under load by decreasing
 minimum scheduling granularity


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Mon, Sep 13, 2010 at 11:23 AM, Ingo Molnar <mingo@...e.hu> wrote:
> >
> > Linus, Mathieu, you can test the granularity reduction patch via:
> 
> Hmm. It's a bit hard to judge subjective feelings, especially when you 
> have expectations of improvement, but yes, I think this does improve 
> the the interactive feel when scroll-wheeling around in firefox or 
> chrome.

Yeah. Human perception generally notices the _gradient_ of behavior - 
i.e. the difference between the best-case and worst-case behavior. I.e. 
we notice the max latencies - and those came down distinctly in 
everyone's measurements.

Somewhat paradoxially, 'always slow' is generally felt as an improvement 
over 'sometimes fast, sometimes slow' - even though the latter has a 
better average. (as long as 'slow' is not 'intolerably slow')

> So on the whole I'd trust the actual latency benchmark numbers more, 
> but I _think_ it does translate into actually feeling better too.

Ok, great - would you like to have this in v2.6.36 (in which case feel 
free to pull it now), or v2.6.37?

I'm hopeful that the other patches in the works will give more 
improvements - i dont actually like the relatively high noise that the 
max latencies produce - i think we should be more 
deterministic/dependable there. But those changes are also more complex, 
so they will take a bit more time to finish - and it's definitely 
v2.6.37 fodder.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ