linux-kernel - Re: [RFC] cpuset: add interface to isolated cpus

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:	Thu, 19 Oct 2006 20:17:14 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Paul Jackson <pj@....com>
CC:	Andrew Morton <akpm@...l.org>, Martin Bligh <mbligh@...gle.com>,
	Paul Menage <menage@...gle.com>, Simon.Derr@...l.net,
	linux-kernel@...r.kernel.org,
	Dinakar Guniguntala <dino@...ibm.com>,
	Rohit Seth <rohitseth@...gle.com>, Robin Holt <holt@....com>,
	dipankar@...ibm.com, "Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: Re: [RFC] cpuset: add interface to isolated cpus

Paul Jackson wrote:
> From: Paul Jackson <pj@....com>
> 
> Enable user code to isolate CPUs on a system from the domains that
> determine scheduler load balancing.
> 
> This is already doable using the boot parameter "isolcpus=".  The folks
> running realtime code on production systems, where some nodes are
> isolated for realtime, and some not, and where it is unacceptable
> to reboot to adjust this, need to be able to change which CPUs are
> isolated from the scheduler balancing code on the fly.
> 
> This is done by exposing the kernels cpu_isolated_map as a cpumask
> in the root cpuset directory, in a file called 'isolated_cpus',
> where it can be read and written by sufficiently privileged user code.

This should be done outside cpusets.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/