[torquedev] processor affinity
Prakash.Velayutham at cchmc.org
Sat Jun 2 14:21:09 MDT 2007
I think linux currently supports cpusets. At least, I can see the option
in the Kernel source.
>>> "Toni L. Harbaugh-Blackford [Contr]" <harbaugh at ncifcrf.gov> 06/02/07
3:41 PM >>>
Torque does not assign specific cpus.
On some architectures (Altix, maybe IRIX still) cpusets are implemented,
and these do restrict jobs to a given set of cpus. You many want to
a look at the cpuset code and see if it could be generalized to other
On Sat, 2 Jun 2007, Menshutin Anton wrote:
> Hi list,
> I found that there is no processor affinity in torque. Jobs assigned
> on some cpu's selected by scheduler, could also run on other cpus on
> node. This means that if user lunches more processes or threads on a
> than he has requested, his processes will span over other cpus
> the operating system scheduling policy. Thus he can get more cpu
> than he should. Its clear that this is undesired behavior.
> Nevertheless, starting from linux kernel 2.6 there is a system call
> sched_setaffinity() which enables programmer to tell OS scheduler
not to use
> some cpus. So this is thing one have to add to torque.
> This property is inherited by child process. It is obvious that
> after fork() and before exec() will be enough. The only thing I
don't know -
> where can I get info about cpus assigned to me by scheduler.
> Qstat shows this info in exec_host attribute, and I suppose I can
> string, parse it, find out localhostname and get CPUs numbers. But
> there is a better way for getting this info?
> I'm asking for help from torque-dev mailing list :) Given an advice,
> try to implement and test it myself or may be anybody could send me
> torquedev mailing list
> torquedev at supercluster.org
Toni Harbaugh-Blackford harbaugh at ncifcrf.gov
Advanced Biomedical Computing Center (ABCC)
National Cancer Institute
Contractor - SAIC/Frederick
torquedev mailing list
torquedev at supercluster.org
More information about the torquedev