This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Thu, 2009-10-22 at 10:37 +1100, Chris Samuel wrote:
> ----- "Chris Samuel" <csamuel_at_[hidden]> wrote:
> > Some sample results below for configs not represented
> > on the current website.
> A final example of a more convoluted configuration with
> a Torque job requesting 5 CPUs on a dual Shanghai node
> and has been given a non-contiguous configuration.
> [csamuel_at_tango069 ~]$ cat /dev/cpuset/`cat /proc/$$/cpuset`/cpus
You can better write this as
$ grep Cpus_allowed_list /proc/$$/status
Of course the best way to show it for all processes in a job is (run
this from outside your job)
$ padb -a --proc-summary
> [csamuel_at_tango069 ~]$ ~/local/hwloc/0.9.1rc2/bin/lstopo
> Node#0(15GB) + Socket#0 + L3(6144KB) + L2(512KB) + L1(64KB) + Core#0 + P#0
> Node#1(16GB) + Socket#1 + L3(6144KB)
> L2(512KB) + L1(64KB) + Core#0 + P#4
> L2(512KB) + L1(64KB) + Core#1 + P#5
> L2(512KB) + L1(64KB) + Core#2 + P#6
> L2(512KB) + L1(64KB) + Core#3 + P#7
Does this imply the default is to report on processes in the current
cpuset rather than the entire system? Does anyone else feel that
violates the principal of least surprise?
Ashley Pittman, Bath, UK.
Padb - A parallel job inspection tool for cluster computing