linux-kernel - Re: [RFC] time: xtime

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]

Date:	Fri, 6 May 2011 18:59:13 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Eric Dumazet <eric.dumazet@...il.com>,
	john stultz <johnstul@...ibm.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Paul Mackerras <paulus@...ba.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Anton Blanchard <anton@...ba.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC] time: xtime_lock is held too long

On Fri, May 06, 2011 at 12:18:27PM +0200, Thomas Gleixner wrote:
> > There's actually some potential here. I got a moderate speedup in a
> > database benchmark with this patch recently. The biggest win
> 
> Numbers please.

Low single digit on a hard to improve well tuned workload.

> Well, then we should make sure that they are not.

Ok I will send a patch.

> 
> And looking at a few kernel images the interesting variables
> timekeeper, xtime, wall_to_monotonic are in a consecutive area which
> is not really surprising. Further all images have xtime and
> wall_to_monotonic in the same cacheline, just xtime_lock is somewhere
> else.

I guess it depends a lot on the particular alignment. 
But yes it should be ensured.

> 
> > (needs some cleanups, just for illustration)
> 
> And how's that cleanup going to look like? Making the timekeeping
> internal variables global again is not going to happen. And if you

Why not?  You could of course call some function in the file 
to do the prefetches, but that would seem dumb to me.

> want prefetching those variables in the timer interrupt, then you want
> to prefetch them in any random code path which ends up touching them.

If that code path shows up in profiling. Only the timer interrupt
did so far.

> That's the completely wrong aproach, really. If stuff takes too long,
> then we need to tackle it at the root of the problem and not solve it
> by sprinkling magic prefetches all over the place.

If you have a better way to make it faster please share it.

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