linux-kernel - Re: [RFC PATCH] Turn off the tick even when not idle

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:	Tue, 1 Sep 2009 18:35:34 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Josh Triplett <josh@...htriplett.org>
cc:	linux-kernel@...r.kernel.org, Anton Blanchard <anton@...ba.org>,
	Tim Pepper <lnxninja@...ux.vnet.ibm.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	John Stultz <johnstul@...ibm.com>,
	Jamey Sharp <jamey@...ilop.net>
Subject: Re: [RFC PATCH] Turn off the tick even when not idle

On Tue, 1 Sep 2009, Josh Triplett wrote:

> Thanks; exactly what I hoped to demonstrate.  Actually making the timer
> interrupt go away will require finding a more appropriate place to run
> all the code that otherwise polls periodically, but this patch lets us
> cheat and see the result before that happens. :)

Well not necessarily. Since the process is not doing system calls some of
the checks can be skipped. In order to bring about a quiet state for the
VM one could fold the vm counters and dump the queues. Then maintenance is
unnecessary as long as no system activity occurs on a processor.

> I ran the benchmark at realtime priority, and affinitized to a single
> CPU.  I used ftrace to confirm that after the initial program setup
> (shared library loads, memory allocation, etc), no code runs in the
> kernel during the number-crunching; this makes sense, since I ran at
> higher priority than all the random affinitized kernel threads, and I
> pushed everything else (tasks and interrupts) onto another CPU.

Interesting.

> Long-term I'd like to solve the problem of those kernel threads, but
> realtime priority can mitigate those.  The new interrupt threading bits
> may help with other interrupts and avoid the need to set interrupt
> affinity.  The timer interrupt, though, represents the one and only
> thing I can't mitigate, hence why I'd like to make it go away.

Well it would be best if we can guarantee that there is no system activity
starting. What you have done is analyze all the causes for your particular
situation and mitigated them. Not everyone is a specialist able to figure
out these causes.

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