Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] 0.9.1rc2 is available
From: Ashley Pittman (ashley_at_[hidden])
Date: 2009-10-22 04:53:41


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
> 0,4-7

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
--proc-format=vp=rank,pid,hostname=host,Cpus_allowed_list=cpuset

> [csamuel_at_tango069 ~]$ ~/local/hwloc/0.9.1rc2/bin/lstopo
> System(31GB)
> 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,

-- 
Ashley Pittman, Bath, UK.
Padb - A parallel job inspection tool for cluster computing
http://padb.pittman.org.uk