topology(1)
topology - machine topology information
As shipped in IRIX 6.5.15. Last changed in IRIX 6.5.15.
NAME topology - machine topology information SYNOPSIS topology DESCRIPTION Machine topology information is extracted from the hardware graph. The output of the topology command is not guaranteed to remain constant between releases. The topology command is an editable script that can be customized by the end user. EXAMPLE When executed on a 16 processor Origin2000 named clink, the topology command yields: Machine clink has: 16 cpu's 8 memory nodes 4 routers The cpus are: cpu 0 is /hw/module/1/slot/n1/node/cpubus/0/a cpu 1 is /hw/module/1/slot/n1/node/cpubus/0/b cpu 2 is /hw/module/1/slot/n2/node/cpubus/0/a cpu 3 is /hw/module/1/slot/n2/node/cpubus/0/b cpu 4 is /hw/module/1/slot/n3/node/cpubus/0/a cpu 5 is /hw/module/1/slot/n3/node/cpubus/0/b cpu 6 is /hw/module/1/slot/n4/node/cpubus/0/a cpu 7 is /hw/module/1/slot/n4/node/cpubus/0/b cpu 8 is /hw/module/2/slot/n1/node/cpubus/0/a cpu 9 is /hw/module/2/slot/n1/node/cpubus/0/b cpu 10 is /hw/module/2/slot/n2/node/cpubus/0/a cpu 11 is /hw/module/2/slot/n2/node/cpubus/0/b cpu 12 is /hw/module/2/slot/n3/node/cpubus/0/a cpu 13 is /hw/module/2/slot/n3/node/cpubus/0/b cpu 14 is /hw/module/2/slot/n4/node/cpubus/0/a cpu 15 is /hw/module/2/slot/n4/node/cpubus/0/b The nodes are: node 0 is /hw/module/1/slot/n1/node node 1 is /hw/module/1/slot/n2/node node 2 is /hw/module/1/slot/n3/node node 3 is /hw/module/1/slot/n4/node node 4 is /hw/module/2/slot/n1/node node 5 is /hw/module/2/slot/n2/node node 6 is /hw/module/2/slot/n3/node node 7 is /hw/module/2/slot/n4/node The routers are: /hw/module/1/slot/r1/router /hw/module/1/slot/r2/router /hw/module/2/slot/r1/router /hw/module/2/slot/r2/router The topology is defined by: /hw/module/1/slot/n1/node/link -> /hw/module/1/slot/r1/router /hw/module/1/slot/n2/node/link -> /hw/module/1/slot/r1/router /hw/module/1/slot/n3/node/link -> /hw/module/1/slot/r2/router /hw/module/1/slot/n4/node/link -> /hw/module/1/slot/r2/router /hw/module/2/slot/n1/node/link -> /hw/module/2/slot/r1/router /hw/module/2/slot/n2/node/link -> /hw/module/2/slot/r1/router /hw/module/2/slot/n3/node/link -> /hw/module/2/slot/r2/router /hw/module/2/slot/n4/node/link -> /hw/module/2/slot/r2/router /hw/module/1/slot/r1/router/1 -> /hw/module/2/slot/r1/router /hw/module/1/slot/r1/router/2 -> /hw/module/2/slot/r2/router /hw/module/1/slot/r1/router/4 -> /hw/module/1/slot/n2/node /hw/module/1/slot/r1/router/5 -> /hw/module/1/slot/n1/node /hw/module/1/slot/r1/router/6 -> /hw/module/1/slot/r2/router /hw/module/1/slot/r2/router/1 -> /hw/module/2/slot/r2/router /hw/module/1/slot/r2/router/2 -> /hw/module/2/slot/r1/router /hw/module/1/slot/r2/router/4 -> /hw/module/1/slot/n4/node /hw/module/1/slot/r2/router/5 -> /hw/module/1/slot/n3/node /hw/module/1/slot/r2/router/6 -> /hw/module/1/slot/r1/router /hw/module/2/slot/r1/router/1 -> /hw/module/1/slot/r1/router /hw/module/2/slot/r1/router/2 -> /hw/module/1/slot/r2/router /hw/module/2/slot/r1/router/4 -> /hw/module/2/slot/n2/node /hw/module/2/slot/r1/router/5 -> /hw/module/2/slot/n1/node /hw/module/2/slot/r1/router/6 -> /hw/module/2/slot/r2/router /hw/module/2/slot/r2/router/1 -> /hw/module/1/slot/r2/router /hw/module/2/slot/r2/router/2 -> /hw/module/1/slot/r1/router /hw/module/2/slot/r2/router/4 -> /hw/module/2/slot/n4/node /hw/module/2/slot/r2/router/5 -> /hw/module/2/slot/n3/node /hw/module/2/slot/r2/router/6 -> /hw/module/2/slot/r1/router SEE ALSO hinv(1), hwgraph(4)