Perhaps the Sun n1GE Grid-Engine Software would be useful in this instance?
The tools are really meant to schedule jobs across many machines, with many
CPUs, but you could probably repurpose their scheduling tools to restrict
user jobs to one CPU on a single system with similar ease.
-G
Regards,
Gavin McDonald
EVI Logistic Enterprises
email: me (AT) gavitron (DOT) com
phone: (604) 313-3845
Message
From: redhat-list-bounces (AT) redhat (DOT) com [mailto:redhat-list-
bounces (AT) redhat (DOT) com] Behalf George Magklaras
Sent: Tuesday, May 09, 2006 1:02 AM
To: General Red Hat Linux discussion list
Subject: Re: limiting CPU access per user
A wrapper script that takes what is to be executed, check it out and
then dplace it to a certain CPU(s) comes to mind. Since dplace can also
maintain a global count of all active tasks in each CPU that should not
be a problem for you to check out what happens at your end.
If it's not going to be a wrapper script, then that could form part of
your queue system scripts. We handle this issue by placing the dplace
arguments in our PBS scripts.
Maybe someone has a more straightforward solution, but this is what we do.