linux-kernel - Re: [RFC PATCH 0/4] timers: framework for migration between CPU

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: <1235664169.4948.319.camel@laptop>
Date:	Thu, 26 Feb 2009 17:02:49 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Dipankar Sarma <dipankar@...ibm.com>,
	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	ego@...ibm.com, tglx@...utronix.de, andi@...stfloor.org,
	venkatesh.pallipadi@...el.com, vatsa@...ux.vnet.ibm.com,
	arun@...ux.vnet.ibm.com, Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [RFC PATCH 0/4] timers: framework for migration between CPU

On Thu, 2009-02-26 at 16:45 +0100, Ingo Molnar wrote:

> Yes - but that kind of policy should be coupled and expressed 
> via cpusets. /proc based irq_affinity is just a limited, 
> inflexible hack. All things IRQ partitioning should be handled 
> via cpusets - perhaps via the 'system sets' idea from Peter?

all we got out of that idea was the default_smp_affinity thing
in /proc/irq and a head-ache trying to work out silly details.

Maybe we ought to try again,..

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