linux-kernel - Re: [RFC PATCH] check_preempt_tick should not compare vruntime with wall time

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]

Date:	Mon, 13 Sep 2010 20:03:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	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: [RFC PATCH] check_preempt_tick should not compare vruntime with
 wall time


* Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:

> * Linus Torvalds (torvalds@...ux-foundation.org) wrote:
> > On Mon, Sep 13, 2010 at 9:16 AM, Mathieu Desnoyers
> > <mathieu.desnoyers@...icios.com> wrote:
> > >
> > > OK, the long IRC discussions we just had convinced me that the current scheme
> > > takes things into account by adapting the granularity dynamically, but also got
> > > me to notice that check_preempt seems to compare vruntime with wall time, which
> > > is utterly incorrect. So maybe all my patch was doing was to expose this bug:
> > 
> > Do you have latency numbers for this patch?
> 
> Sure, see below,
> 
> In addition to this patch, [...]

Note, which is a NOP for your latency workload.

> [...] I also used Peter's approach of reducing the minimum granularity

Ok, that's the very first patch i sent yesterday morning - so we also 
have my numbers that it reduces latencies.

To move things along i'll apply it with your Reported-by and Acked-by 
line, ok?

We can also work on the other, more complex things after that, but first 
lets make some progress on the latency front ...

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/