linux-kernel - Re: RFC: THE OFFLINE SCHEDULER

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]

Message-ID: <alpine.DEB.1.10.0908281551450.17784@gentwo.org>
Date:	Fri, 28 Aug 2009 15:52:37 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
cc:	Gregory Haskins <ghaskins@...ell.com>,
	Rik van Riel <riel@...hat.com>,
	Chris Friesen <cfriesen@...tel.com>,
	raz ben yehuda <raziebe@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
	peterz@...radead.org, maximlevitsky@...il.com, efault@....de,
	wiseman@...s.biu.ac.il, linux-kernel@...r.kernel.org,
	linux-rt-users@...r.kernel.org
Subject: Re: RFC: THE OFFLINE SCHEDULER

On Fri, 28 Aug 2009, Thomas Gleixner wrote:

> Right, and I think we can get there. The timer can be eliminated with
> some work. Faults shouldn't happen on that CPU and all other
> interrupts can be kept away with proper affinity settings. Softirqs
> should not happen on such a CPU either as there is neither a hardirq
> nor a user space task triggering them. Same applies for timers. So
> there are some remaining issues like IPIs, but I'm pretty sure that
> they can be tamed to zero as well.

There are various timer generated thingies like vm statistics, slab queue
management and device specific things that run on each processor.

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