linux-kernel - Restricting Processor Usage

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-next>] [day] [month] [year] [list]

Date:	Fri, 09 May 2008 09:27:34 -0700
From:	Brian McGrew <brian@...ionpro.com>
To:	<linux-kernel@...r.kernel.org>
Subject: Restricting Processor Usage

Now that I've got sched_(set|get)affinity working (thank you all for all of
the great help), I need to figure out how to unload the processors in the
machine.

When the system comes up, by default the general system load is spread
across all the processors, even when it is idle.  I'm looking for a way to
force everything on the system (kernel, X, gnome, etc.) to run on only one
processor and leave the remaining processors idea for thread assignments.
I'm doing very heavy image processing and need all the power I can get out
of each CPU.

How can I do this?  Just make the system as a whole run on only one CPU but
allow processes and threads that I create to set their affinity to the
remaining unloaded CPU's???

-brian

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