maupuquaemeliseg.netlify.com

If you enter the no hw-module switch switchnumber slot slotnumber oversubscription command to configure non-oversubscription mode (performance mode), then only ports 1, 5, 9, and 13 are configurable; the other ports on the module are disabled.

• No Hw-module Slot 1 Oversubscription Port-group 1
• No Hw-module Switch 1 Slot 1 Oversubscription Port-group 1

Abstract

• No Hw Module Switch 1 Slot 1 Oversubscription Port Group 1, online poker hong kong, demo slots mayan secret, tournoi poker femmes.
• No Hw Module Slot 1 Oversubscription, macau casino skyfall, first council casino newkirk ok tickets, sandstone slot canyon arizona.
• No Deposit Bonus Terms and Conditions hw-module slot 1 oversubscription An additional traditional rule is that loose slots are put on the major aisles in the casinos, again so that more people could see winning jackpots and be roused to play.
• The 1:1 ratio means no oversubscription of the PCIe lanes from the processors and results in maximum NVMe drive bandwidth. 1610-4P Slot 1 (Riser 1) PCIe x16 1.

The ThinkSystem SR650 is a mainstream 2U 2-socket server with industry-leading reliability, management, and security features, and is designed to handle a wide range of workloads.

New to the SR650 is support for up to 24 NVMe solid-state drives. With this support, the SR650 is an excellent choice for workloads that need large amounts of low-latency high-bandwidth storage, including virtualized clustered SAN solutions, software-defined storage, and applications leveraging NVMe over Fabrics (NVMeOF).

This article describes the three new configurations available for the SR650:

• 16 NVMe drives + 8 SAS/SATA drives
• 20 NVMe drives
• 24 NVMe drives

You can also learn about the offerings by watching the walk-through video below.

Change History

Changes in the April 16 update:

• Noted which second-generation Intel Xeon processors are not supported - Ordering information section

Walk-through video with David Watts and Patrick Caporale

Introduction

The Lenovo ThinkSystem SR650 is a mainstream 2U 2-socket server with industry-leading reliability, management, and security features, and is designed to handle a wide range of workloads.

New to the SR650 is support for up to 24 NVMe solid-state drives. With this support, the SR650 is an excellent choice for workloads that need large amounts of low-latency high-bandwidth storage, including virtualized clustered SAN solutions, software-defined storage, and applications leveraging NVMe over Fabrics (NVMeOF).

Figure 1. ThinkSystem SR650 with 24 NVMe drives

Three new configurations are now available:

• 16 NVMe drives + 8 SAS/SATA drives
• 20 NVMe drives
• 24 NVMe drives

NVMe (Non-Volatile Memory Express) is a technology that overcomes SAS/SATA SSD performance limitations by optimizing hardware and software to take full advantage of flash technology. Intel Xeon processors efficiently transfer data in fewer clock cycles with the NVMe optimized software stack compared to the legacy AHCI stack, thereby reducing latency and overhead. NVMe SSDs connect directly to the processor via the PCIe bus, further reducing latency. NVMe drives are characterized by very high bandwidth and very low latency.

Ordering information

These configurations are available configure-to-order (CTO) in the Lenovo Data Center Solution Configurator (DCSC), https://dcsc.lenovo.com. The following table lists the feature codes related to the NVMe drive subsystem. The configurator will derive any additional components that are needed.

Field upgrades: The 20x NVMe and 24x NVMe drive configurations are also available as field upgrades as described in the Field upgrades section.

Table 1. Feature codes for CTO orders

Feature code	Description
PCIe Switch Adapters
B22D	ThinkSystem 810-4P NVMe Switch Adapter (PCIe x8 adapter with four x4 drive connectors)
AUV2	ThinkSystem 1610-4P NVMe Switch Adapter (PCIe x16 adapter with four x4 drive connectors)
B4PA	ThinkSystem 1610-8P NVMe Switch Adapter (PCIe x16 adapter with four connectors to connect to eight drives)
NVMe Backplane
B4PC	ThinkSystem SR650 2.5' NVMe 8-Bay Backplane
Riser Cards
AUR3	ThinkSystem SR550/SR590/SR650 x16/x8 PCIe FH Riser 1 Kit (x16+x8 PCIe Riser for Riser 1, for 16 and 20-drive configurations)
B4PB	ThinkSystem SR650 x16/x8/x16 PCIe Riser1 (x16+x8+x16 PCIe Riser for Riser 1, for 24-drive configurations)
AURC	ThinkSystem SR550/SR590/SR650 (x16/x8)/(x16/x16) PCIe FH Riser 2 Kit (x16+x16 PCIe Riser for Riser 2, for all three configurations)

Note the following requirements for any of the three NVMe-rich configurations:

• Two processors
• No high-thermal processors:
  • 200 W or 205 W TDP are not supported
  • Gold 6126T, Gold 6144, Gold 6146, or Platinum 8160T processors are not supported
  • Gold 6230N, Gold 6240Y, and Gold 6244 processors are not supported
• No GPU adapters installed
• No PCIe flash adapters installed
• No PCIe adapters with more than 25 W TDP installed
• 1100 W or 1600 W power supplies installed.
• Ambient temperature of up to 30 °C (86 °F)
• If a fan fails and the ambient temperature is above 27 °C, system performance may be reduced.

Although not required, it is expected that these configurations will be fully populated with NVMe drives. Maximum performance is achieved when all NVMe drive bays are filled with drives.

To verify support and ensure that the right power supply is chosen for optimal performance, validate your server configuration using the latest version of the Lenovo Capacity Planner:
http://datacentersupport.lenovo.com/us/en/solutions/lnvo-lcp

Supported NVMe drives

See the ThinkSystem SR650 product guide for the complete list of NVMe drives that are supported in the server: https://lenovopress.com/lp0644#drives-for-internal-storage

The NVMe drives listed in the following table are not supported in the three NVMe-rich configurations.

Table 2. NVMe drives that are not supported in the 16, 20, and 24x NVMe drive configurations

Part number	Feature code	Description
Unsupported NVMe drives
7SD7A05770	B11L	ThinkSystem U.2 Intel P4600 6.4TB Mainstream NVMe PCIe3.0 x4 Hot Swap SSD
7N47A00984	AUV0	ThinkSystem U.2 PM963 1.92TB Entry NVMe PCIe 3.0 x4 Hot Swap SSD
7N47A00985	AUUU	ThinkSystem U.2 PM963 3.84TB Entry NVMe PCIe 3.0 x4 Hot Swap SSD
7N47A00095	AUUY	ThinkSystem U.2 PX04PMB 960GB Mainstream NVMe PCIe 3.0 x4 Hot Swap SSD
7N47A00096	AUMF	ThinkSystem U.2 PX04PMB 1.92TB Mainstream NVMe PCIe 3.0 x4 Hot Swap SSD
7XB7A05923	AWG6	ThinkSystem U.2 PX04PMB 800GB Performance NVMe PCIe 3.0 x4 Hot Swap SSD
7XB7A05922	AWG7	ThinkSystem U.2 PX04PMB 1.6TB Performance NVMe PCIe 3.0 x4 Hot Swap SSD

Configuration 1: 16x NVMe drives + 8x SAS/SATA

The 16x NVMe drive configuration has the following features:

• 16 NVMe 2.5-inch drive bays plus eight SAS/SATA 2.5-inch drive bays. All drives are hot-swap from the front of the server (provided the operating system supports hot-swap).
• The NVMe drives are connected to the processors either via NVMe Switch Adapters or via the onboard NVMe connectors on the system board of the server.
• The eight SAS/SATA drive bays are connected to a supported 8-port RAID adapter or SAS HBA.
• One PCIe x16 slot is available for high-speed networking such as a 100 GbE adapter, InfiniBand or OPA adapter. If you elect not to configure the eight SAS/SATA drive bays, then you can free up an additional x8 slot for a second networking adapter.
• The LOM (LAN on Motherboard) slot is also available for 1Gb or 10Gb Ethernet connections. Supported LOM adapters are the following:
  • ThinkSystem 1Gb 2-port RJ45 LOM
  • ThinkSystem 1Gb 4-port RJ45 LOM
  • ThinkSystem 10Gb 2-port Base-T LOM
  • ThinkSystem 10Gb 2-port SFP+ LOM
  • ThinkSystem 10Gb 4-port Base-T LOM
  • ThinkSystem 10Gb 4-port SFP+ LOM
• Additional support for one or two M.2 drives, if needed

The 16x NVMe drive configuration has the following performance characteristics:

• Balanced NVMe configuration. In this 16-NVMe drive configuration, each processor is connected to 8 drives. Such a balanced configuration ensures maximum performance by ensuring the processors are equally occupied handling I/O requests to and from the NVMe drives.
• No oversubscription. Lenovo NVMe drives connect using four PCIe lanes, and in this configuration, each drive is allocated 4 lanes from the processor. The 1:1 ratio means no oversubscription of the PCIe lanes from the processors and results in maximum NVMe drive bandwidth.

In the 16x NVMe drive configuration, the drive bays are configured as follows:

• Bays 0-15: NVMe drives
• Bays 16-23: SAS or SATA drives

The PCIe slots in the server are configured as follows:

• Slot 1: 1610-4P NVMe Switch Adapter
• Slot 2: Not present
• Slot 3: Supported RAID adapter for SAS/SATA drives
• Slot 4: 810-4P NVMe Switch Adapter
• Slot 5: Available x16 slot
• Slot 6: 1610-4P NVMe Switch Adapter
• Slot 7 (internal slot): 810-4P NVMe Switch Adapter

The front and rear views of the SR650 with 16x NVMe drives and 8x SAS/SATA drives is shown in the following figure.

Figure 2. SR650 front and rear views of the 16-NVMe drive configuration

The following figure shows a block diagram of how the PCIe lanes are routed from the processors to the NVMe drives.

Figure 3. SR650 block diagram of the 16-NVMe drive configuration

The details of the connections are listed in the following table.

Table 3. Drive connections

Drive bay	Drive type	Drive lanes	Adapter	Slot	Host lanes	CPU
0	NVMe	PCIe x4	Onboard NVMe port	None	PCIe x8	2
1	NVMe	PCIe x4				2
2	NVMe	PCIe x4	Onboard NVMe port	None	PCIe x8	2
3	NVMe	PCIe x4				2
4	NVMe	PCIe x4	1610-4P	Slot 6 (Riser 2)	PCIe x16	2
5	NVMe	PCIe x4				2
6	NVMe	PCIe x4				2
7	NVMe	PCIe x4				2
8	NVMe	PCIe x4	810-4P	Slot 4 (vertical)	PCIe x8	1
9	NVMe	PCIe x4				1
10	NVMe	PCIe x4	810-4P	Slot 7 (internal)	PCIe x8	1
11	NVMe	PCIe x4				1
12	NVMe	PCIe x4	1610-4P	Slot 1 (Riser 1)	PCIe x16	1
13	NVMe	PCIe x4				1
14	NVMe	PCIe x4				1
15	NVMe	PCIe x4				1
16	SAS or SATA		RAID 8i	Slot 3 (Riser 1)	PCIe x8	1
17	SAS or SATA					1
18	SAS or SATA					1
19	SAS or SATA					1
20	SAS or SATA					1
21	SAS or SATA					1
22	SAS or SATA					1
23	SAS or SATA					1

Configuration 2: 20x NVMe drives

The 20x NVMe drive configuration has the following features:

• 20 NVMe 2.5-inch drive bays. All drives are hot-swap from the front of the server (provided the operating system supports hot-swap). The other 4 bays are unavailable and are covered by a 4-bay blank.
• The NVMe drives are connected to the processors either via NVMe Switch Adapters or via the onboard NVMe connectors on the system board of the server.
• One PCIe x8 slot is available for networking or other needs. The LOM (LAN on Motherboard) slot is also available for 1Gb or 10Gb Ethernet connections. Supported LOM adapters are the following:
  • ThinkSystem 1Gb 2-port RJ45 LOM
  • ThinkSystem 1Gb 4-port RJ45 LOM
  • ThinkSystem 10Gb 2-port Base-T LOM
  • ThinkSystem 10Gb 2-port SFP+ LOM
  • ThinkSystem 10Gb 4-port Base-T LOM
  • ThinkSystem 10Gb 4-port SFP+ LOM
• Additional support for one or two M.2 drives, if needed

The 20x NVMe drive configuration has the following performance characteristics:

• No oversubscription. Lenovo NVMe drives connect using four PCIe lanes, and in this configuration, each drive is allocated 4 lanes from the processor. The 1:1 ratio means no oversubscription of the PCIe lanes from the processors and results in maximum NVMe drive bandwidth.
• Near-balanced NVMe configuration. Unlike the 16-drive and 24-drive configurations, that 20-drive configuration has eight NVMe drives connected to processor 1, and 12 NVMe drives connected to processor 2. As a result, we recommend you to only choose this configuration if you need the additional capacity that four drives provide above the 16-drive configuration, and your workload can fully operate without an equal number of drives connected to each processor.

The PCIe slots in the server are configured as follows:

• Slot 1: 1610-4P NVMe Switch Adapter
• Slot 2: Not present
• Slot 3: Available x8 slot
• Slot 4: 810-4P NVMe Switch Adapter
• Slot 5: 1610-4P NVMe Switch Adapter
• Slot 6: 1610-4P NVMe Switch Adapter
• Slot 7 (internal slot): 810-4P NVMe Switch Adapter

The front and rear views of the SR650 with 20x NVMe drives is shown in the following figure.

Figure 4. SR650 front and rear views of the 20-NVMe drive configuration

The following figure shows a block diagram of how the PCIe lanes are routed from the processors to the NVMe drives.

Figure 5. SR650 block diagram of the 20-NVMe drive configuration

The details of the connections are listed in the following table.

Table 4. Drive connections

Drive bay	Drive type	Drive lanes	Adapter		Slot	Host lanes	CPU
0	NVMe	PCIe x4	Onboard NVMe port		None	PCIe x8	2
1	NVMe	PCIe x4					2
2	NVMe	PCIe x4	Onboard NVMe port		None	PCIe x8	2
3	NVMe	PCIe x4					2
4	NVMe	PCIe x4	1610-4P		Slot 6 (Riser 2)	PCIe x16	2
5	NVMe	PCIe x4					2
6	NVMe	PCIe x4					2
7	NVMe	PCIe x4					2
8	NVMe	PCIe x4	1610-4P		Slot 5 (Riser 2)	PCIe x16	2
9	NVMe	PCIe x4					2
10	NVMe	PCIe x4					2
11	NVMe	PCIe x4					2
12	NVMe	PCIe x4	810-4P		Slot 4 (vertical)	PCIe x8	1
13	NVMe	PCIe x4					1
14	NVMe	PCIe x4	810-4P		Slot 7 (internal)	PCIe x8	1
15	NVMe	PCIe x4					1
16	NVMe	PCIe x4	1610-4P		Slot 1 (Riser 1)	PCIe x16	1
17	NVMe	PCIe x4					1
18	NVMe	PCIe x4					1
19	NVMe	PCIe x4					1
20	Blank bay - no connection
21	Blank bay - no connection
22	Blank bay - no connection
23	Blank bay - no connection

Configuration 3: 24x NVMe drives

The 24x NVMe drive configuration has the following features:

• 24 NVMe 2.5-inch drive bays. All drives are hot-swap from the front of the server (provided the operating system supports hot-swap).
• The NVMe drives are connected to the processors via NVMe Switch Adapters. The onboard NVMe connectors are routed to a riser card installed in Riser slot 1.
• Two x16 slots (one connected to each processor) are available for high-speed networking such as a 100 GbE adapter, InfiniBand or OPA adapter.
• The LOM (LAN on Motherboard) slot is also available for 1Gb or 10Gb Ethernet connections. Supported LOM adapters are the following:
  • ThinkSystem 1Gb 2-port RJ45 LOM
  • ThinkSystem 1Gb 4-port RJ45 LOM
  • ThinkSystem 10Gb 2-port Base-T LOM
  • ThinkSystem 10Gb 2-port SFP+ LOM
  • ThinkSystem 10Gb 4-port Base-T LOM
  • ThinkSystem 10Gb 4-port SFP+ LOM
• Additional support for one or two M.2 drives, if needed

The 24x NVMe drive configuration has the following performance characteristics:

• Balanced NVMe configuration. In this 24-NVMe drive configuration, each processor is connected to 12 drives. Such a balanced configuration provides maximum performance by ensuring the processors are equally occupied handling I/O requests to and from the NVMe drives.
• 2:1 oversubscription. Lenovo NVMe drives connect using four PCIe lanes, and in this configuration each drive is allocated 2 lanes from the processor, resulting in a 2:1 oversubscription of the PCIe lanes. With 24 drives, there are simply not enough PCIe lanes in a two-socket server to support no oversubscription. As a result, the design objective is to minimize the oversubscription while still maintaining balance across all lanes.
• Balanced open slots. This configuration has two open PCIe x16 slots, one connected to each processor. These slots could be used for a pair of high-speed network cards and the result would be balanced configuration.

The PCIe slots in the server are configured as follows:

• Slot 1: 1610-8P NVMe Switch Adapter
• Slot 2: 810-4P NVMe Switch Adapter
• Slot 3: Available x16 slot
• Slot 4: 810-4P NVMe Switch Adapter
• Slot 5: Available x16 slot
• Slot 6: 810-4P NVMe Switch Adapter
• Slot 7 (internal slot): 810-4P NVMe Switch Adapter

The front and rear views of the SR650 with 24x NVMe drives is shown in the following figure.

Figure 6. SR650 front and rear views of the 24-NVMe drive configuration

The following figure shows a block diagram of how the PCIe lanes are routed from the processors to the NVMe drives.

Figure 7. SR650 block diagram of the 24-NVMe drive configuration

The details of the connections are listed in the following table.

Table 5. Drive connections

Drive bay	Drive type	Drive lanes	Adapter		Slot	Host lanes	CPU
0	NVMe	PCIe x4	810-4P		Slot 6 (Riser 2)	PCIe x8	2
1	NVMe	PCIe x4
2	NVMe	PCIe x4					2
3	NVMe	PCIe x4
4	NVMe	PCIe x4	1610-8P		Slot 1 (Riser 1)	PCIe x16 (from onboard NVMe ports)	2
5	NVMe	PCIe x4
6	NVMe	PCIe x4					2
7	NVMe	PCIe x4
8	NVMe	PCIe x4					2
9	NVMe	PCIe x4
10	NVMe	PCIe x4					2
11	NVMe	PCIe x4
12	NVMe	PCIe x4	810-4P		Slot 4 (vertical)	PCIe x8	1
13	NVMe	PCIe x4
14	NVMe	PCIe x4					1
15	NVMe	PCIe x4
16	NVMe	PCIe x4	810-4P		Slot 7 (internal)	PCIe x8	1
17	NVMe	PCIe x4
18	NVMe	PCIe x4					1
19	NVMe	PCIe x4
20	NVMe	PCIe x4	810-4P		Slot 2 (Riser 1)	PCIe x8	1
21	NVMe	PCIe x4
22	NVMe	PCIe x4					1
23	NVMe	PCIe x4

Field upgrades

The following two field upgrade option kits are available to upgrade existing SAS/SATA or AnyBay drive configurations based on the 24x 2.5' chassis (feature code AUVV) to either the 20-drive or 24-drive NVMe configurations.

Table 6. Field upgrades

Part number	Feature code	Description
4XH7A09819	B64L	ThinkSystem SR650 U.2 20-Bays Upgrade Kit
4XH7A08810	B64K	ThinkSystem SR650 U.2 24-Bays Upgrade Kit

These kits include drive backplanes and required NVMe cables, power cables, drive bay fillers, and NVMe switch adapters.

No 16-drive upgrade kit: There is no upgrade kit for the 16x NVMe drive configuration.

The ThinkSystem SR650 U.2 20-Bays Upgrade Kit includes the following components:

• Two 810-4P NVMe Switch Adapters
• Three 1610-4P NVMe Switch Adapters
• One x16/x8 PCIe Riser for Riser 1
• One x16/x16 PCIe Riser for Riser 2
• Three 8-bay NVMe drive backplanes
• One 4-bay drive bay filler
• NVMe and power cables
• Brackets and screws
• Drive bay labels for the front bezel

The ThinkSystem SR650 U.2 24-Bays Upgrade Kit includes the following components:

• Four 810-4P NVMe Switch Adapters
• One 1610-8P NVMe Switch Adapter
• One x16/x8/x16 PCIe Riser for Riser 1
• One x16/x16 PCIe Riser for Riser 2
• Three 8-bay NVMe drive backplanes
• NVMe and power cables
• Brackets and screws
• Drive bay labels for the front bezel

Further information

For more information, see these resources:

• ThinkSystem SR650 product guide
  https://lenovopress.com/lp0644-lenovo-thinksystem-sr650-server
• Product Guides for ThinkSystem NVMe drives:
  https://lenovopress.com/servers/options/drives#term=nvme&rt=product-guide
• Paper, Implementing NVMe Drives on Lenovo Servers
  https://lenovopress.com/lp0508-implementing-nvme-drives-on-lenovo-servers
• Paper, Comparing the Effect of PCIe Host Connections on NVMe Drive Performance
  https://lenovopress.com/lp0865-comparing-the-effect-of-pcie-host-connections-on-nvme-drive-performance
• Data Center Solution Configurator (DCSC) configurator
  https://dcsc.lenovo.com/

Related product families

Product families related to this document are the following:

Trademarks

Lenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web at https://www.lenovo.com/us/en/legal/copytrade/.

The following terms are trademarks of Lenovo in the United States, other countries, or both:
Lenovo®
AnyBay®
ThinkSystem

The following terms are trademarks of other companies:

Intel® and Xeon® are trademarks of Intel Corporation or its subsidiaries.

Other company, product, or service names may be trademarks or service marks of others.

Table of Contents

Name

prun - Execute serial and parallel jobs with the PMIxReference Server.

Synopsis

Single Process Multiple Data (SPMD) Model:

prun [ options ] <program> [ <args> ]

Multiple Instruction Multiple Data(MIMD) Model:

prun [ global_options ] [ local_options1 ]
<program1> [ <args1> ] : [ local_options2 ]
<program2> [ <args2> ] : ... :
[ local_optionsN ]
<programN> [ <argsN> ]

Note that in both models, invoking prun via an absolutepath name is equivalent to specifying the --prefix option with a <dir> valueequivalent to the directory where prun resides, minus its last subdirectory. For example:

No Hw-module Slot 1 Oversubscription Port-group 1

% /usr/local/bin/prun ...

is equivalent to

% prun --prefix /usr/local

Quick Summary

If you are simply looking for how to run an application,you probably want to use a command line of the following form:

% prun[ -np X ] [ --hostfile <filename> ] <program>

This will run X copies of <program> in your current run-time environment(if running under a supported resource manager, PSRVR’s prun will usuallyautomatically use the corresponding resource manager process starter, asopposed to, for example, rsh or ssh, which require the use of a hostfile,or will default to running all X copies on the localhost), scheduling (bydefault) in a round-robin fashion by CPU slot. See the rest of this pagefor more details.

Please note that prun automatically binds processes. Threebinding patterns are used in the absence of any further directives:

Bindto core:

when the number of processes is <= 2

Bind to socket:

when thenumber of processes is > 2

Bind to none:

when oversubscribed

If yourapplication uses threads, then you probably want to ensure that you areeither not bound at all (by specifying --bind-to none), or bound to multiplecores using an appropriate binding level or specific number of processingelements per application process.

Options

prun will send the name ofthe directory where it was invoked on the local node to each of the remotenodes, and attempt to change to that directory. See the 'Current WorkingDirectory' section below for further details.

<program>

The program executable.This is identified as the first non-recognized argument to prun.

<args>

Passthese run-time arguments to every new process. These must always be thelast arguments to prun. If an app context file is used, <args> will be ignored.

-h, --help

Display help for this command

-q, --quiet

Suppress informativemessages from prun during application execution.

-v, --verbose

Be verbose

-V, --version

Print version number. If no other arguments are given, thiswill also cause prun to exit.

-N <num>

Launch num processes per node on all allocated nodes (synonym for npernode).

-display-map, --display-map

Display a table showing the mapped location ofeach process prior to launch.

-display-allocation, --display-allocation

Displaythe detected resource allocation.

-output-proctable, --output-proctable

Outputthe debugger proctable after launch.

-max-vm-size, --max-vm-size <size>

Numberof processes to run.

-novm, --novm

Execute without creating an allocation-spanningvirtual machine (only start daemons on nodes hosting application procs).

-hnp, --hnp <arg0>

Specify the URI of the psrvr process, or the name of thefile (specified as file:filename) that contains that info.

Use one ofthe following options to specify which hosts (nodes) within the psrvr torun on.

-H, -host, --host <host1,host2,...,hostN>

List of hosts on which to invokeprocesses.

-hostfile, --hostfile <hostfile>

Provide a hostfile to use.

-default-hostfile,--default-hostfile <hostfile>

Provide a default hostfile.

-machinefile, --machinefile<machinefile>

Synonym for -hostfile.

-cpu-set, --cpu-set <list>

Restrict launchedprocesses to the specified logical cpus on each node (comma-separated list).Note that the binding options will still apply within the specified envelope- e.g., you can elect to bind each process to only one cpu within the specifiedcpu set.

The following options specify the number of processes to launch.Note that none of the options imply a particular binding policy - e.g., requestingN processes for each socket does not imply that the processes will be boundto the socket.

-c, -n, --n, -np <#>

Run this many copies of the program on thegiven nodes. This option indicates that the specified file is an executableprogram and not an application context. If no value is provided for thenumber of copies to execute (i.e., neither the '-np' nor its synonyms areprovided on the command line), prun will automatically execute a copy ofthe program on each process slot (see below for description of a 'processslot'). This feature, however, can only be used in the SPMD model and willreturn an error (without beginning execution of the application) otherwise. -<>

Launch N times the number of objects of the specified type on each node.

-npersocket, --npersocket <#persocket>

On each node, launch this many processestimes the number of processor sockets on the node. The -npersocket optionalso turns on the -bind-to-socket option. (deprecated in favor of --map-by ppr:n:socket)

-npernode, --npernode <#pernode>

On each node, launch this many processes.(deprecated in favor of --map-by ppr:n:node)

-pernode, --pernode

On each node,launch one process -- equivalent to -npernode 1. (deprecated in favor of --map-byppr:1:node)

To map processes:

--map-by <foo>

Map to the specified object,defaults to socket. Supported options include slot, hwthread, core, L1cache,L2cache, L3cache, socket, numa, board, node, sequential, distance, andppr. Any object can include modifiers by adding a : and any combinationof PE=n (bind n processing elements to each proc), SPAN (load balance theprocesses across the allocation), OVERSUBSCRIBE (allow more processes ona node than processing elements), and NOOVERSUBSCRIBE. This includes PPR,where the pattern would be terminated by another colon to separate it fromthe modifiers.

-bycore, --bycore

Map processes by core (deprecated in favorof --map-by core)

-byslot, --byslot

Map and rank processes round-robin by slot.

-nolocal, --nolocal

Do not run any copies of the launched application onthe same node as prun is running. This option will override listing thelocalhost with --host or any other host-specifying mechanism.

-nooversubscribe,--nooversubscribe

Do not oversubscribe any nodes; error (without startingany processes) if the requested number of processes would cause oversubscription.This option implicitly sets 'max_slots' equal to the 'slots' value foreach node. (Enabled by default).

-oversubscribe, --oversubscribe

Nodes areallowed to be oversubscribed, even on a managed system, and overloadingof processing elements.

-bynode, --bynode

Launch processes one per node, cyclingby node in a round-robin fashion. This spreads processes evenly among nodesand assigns ranks in a round-robin, 'by node' manner.

-cpu-list, --cpu-list <cpus>

List of processor IDs to bind processes to [default=NULL].

To orderprocesses’ ranks:

--rank-by <foo>

Rank in round-robin fashion according to thespecified object, defaults to slot. Supported options include slot, hwthread,core, L1cache, L2cache, L3cache, socket, numa, board, and node.

Forprocess binding:

--bind-to <foo>

Bind processes to the specified object, defaultsto core. Supported options include slot, hwthread, core, l1cache, l2cache,l3cache, socket, numa, board, and none.

-cpus-per-proc, --cpus-per-proc <#perproc>

Bind each process to the specified number of cpus. (deprecated in favorof --map-by <obj>:PE=n)

-cpus-per-rank, --cpus-per-rank <#perrank>

Alias for -cpus-per-proc.(deprecated in favor of --map-by <obj>:PE=n)

-bind-to-core, --bind-to-core

Bind processesto cores (deprecated in favor of --bind-to core)

-bind-to-socket, --bind-to-socket

Bind processes to processor sockets (deprecated in favor of --bind-to socket)

-report-bindings, --report-bindings

Report any bindings for launched processes.

For rankfiles:

-rf, --rankfile <rankfile>

Provide a rankfile file.

To manage standard I/O:

-output-filename, --output-filename <filename>

Redirectthe stdout, stderr, and stddiag of all processes to a process-unique versionof the specified filename. Any directories in the filename will automaticallybe created. Each output file will consist of filename.id, where the id willbe the processes’ rank, left-filled with zero’s for correct ordering in listings.

-stdin, --stdin <rank>

The rank of the process that is to receive stdin. Thedefault is to forward stdin to rank 0, but this option can be used to forwardstdin to any process. It is also acceptable to specify none, indicatingthat no processes are to receive stdin.

-merge-stderr-to-stdout, --merge-stderr-to-stdout

Merge stderr to stdout for each process.

-tag-output, --tag-output

Tag eachline of output to stdout, stderr, and stddiag with [jobid, MCW_rank]<stdxxx>indicating the process jobid and rank of the process that generated theoutput, and the channel which generated it.

-timestamp-output, --timestamp-output

Timestamp each line of output to stdout, stderr, and stddiag.

-xml, --xml

Provide all output to stdout, stderr, and stddiag in an xml format.

-xml-file,--xml-file <filename>

Provide all output in XML format to the specified file.

-xterm, --xterm <ranks>

Display the output from the processes identified bytheir ranks in separate xterm windows. The ranks are specified as a comma-separatedlist of ranges, with a -1 indicating all. A separate window will be createdfor each specified process. Note: xterm will normally terminate the windowupon termination of the process running within it. However, by adding a'!' to the end of the list of specified ranks, the proper options willbe provided to ensure that xterm keeps the window open after the processterminates, thus allowing you to see the process’ output. Each xterm windowwill subsequently need to be manually closed. Note: In some environments,xterm may require that the executable be in the user’s path, or be specifiedin absolute or relative terms. Thus, it may be necessary to specify a localexecutable as './foo' instead of just 'foo'. If xterm fails to find the executable,prun will hang, but still respond correctly to a ctrl-c. If this happens,please check that the executable is being specified correctly and try again.

To manage files and runtime environment:

-path, --path <path>

<path> thatwill be used when attempting to locate the requested executables. Thisis used prior to using the local PATH setting.

--prefix <dir>

Prefix directorythat will be used to set the PATH and LD_LIBRARY_PATH on the remote nodebefore invoking the target process. See the 'Remote Execution' section,below.

--noprefix

Disable the automatic --prefix behavior

-s, --preload-binary

Copy the specified executable(s) to remote machines prior to starting remoteprocesses. The executables will be copied to the session directory and willbe deleted upon completion of the job.

--preload-files <files>

Preload thecomma separated list of files to the current working directory of the remotemachines where processes will be launched prior to starting those processes.

-set-cwd-to-session-dir, --set-cwd-to-session-dir

Set the working directory of thestarted processes to their session directory.

-wd <dir>

Synonym for -wdir.

-wdir <dir>

Change to the directory <dir> before the user’s program executes.See the 'Current Working Directory' section for notes on relative paths.Note: If the -wdir option appears both on the command line and in an applicationcontext, the context will take precedence over the command line. Thus, ifthe path to the desired wdir is different on the backend nodes, then itmust be specified as an absolute path that is correct for the backend node.

-x <env>

Export the specified environment variables to the remote nodesbefore executing the program. Only one environment variable can be specifiedper -x option. Existing environment variables can be specified or new variablenames specified with corresponding values. For example: % prun -x DISPLAY-x OFILE=/tmp/out ...

The parser for the -x option is not very sophisticated; it does not evenunderstand quoted values. Users are advised to set variables in the environment,and then use -x to export (not define) them.

Setting MCA parameters:

-gpmca, --gpmca <key> <value>

Pass global MCA parameters that are applicableto all contexts. <key> is the parameter name; <value> is the parameter value.

-pmca, --pmca <key> <value>

Send arguments to various MCA modules. See the 'MCA'section, below.

-am <arg0>

Aggregate MCA parameter set file list.

-tune,--tune <tune_file>

Specify a tune file to set arguments for various MCA modulesand environment variables. See the 'Setting MCA parameters and environmentvariables from file' section, below.

For debugging:

-debug, --debug

Invokethe user-level debugger indicated by the orte_base_user_debugger MCA parameter.

--get-stack-traces

When paired with the --timeout option, prun will obtainand print out stack traces from all launched processes that are still alivewhen the timeout expires. Note that obtaining stack traces can take a littletime and produce a lot of output, especially for large process-count jobs.

-debugger, --debugger <args>

Sequence of debuggers to search for when --debugis used (i.e. a synonym for orte_base_user_debugger MCA parameter).

--timeout<seconds>

The maximum number of seconds that prun will run. After this manyseconds, prun will abort the launched job and exit with a non-zero exitstatus. Using --timeout can be also useful when combined with the --get-stack-tracesoption.

-tv, --tv

Launch processes under the TotalView debugger. Deprecatedbackwards compatibility flag. Synonym for --debug.

There are also otheroptions:

--allow-run-as-root

Allow prun to run when executed by the root user(prun defaults to aborting when launched as the root user).

--app <appfile>

Provide an appfile, ignoring all other command line options.

-cf, --cartofile<cartofile>

Provide a cartography file.

-continuous, --continuous

Job is torun until explicitly terminated.

-disable-recovery, --disable-recovery

Disablerecovery (resets all recovery options to off).

-do-not-launch, --do-not-launch

Perform all necessary operations to prepare to launch the application,but do not actually launch it.

-do-not-resolve, --do-not-resolve

Do not attemptto resolve interfaces.

-enable-recovery, --enable-recovery

Enable recoveryfrom process failure [Default = disabled].

-index-argv-by-rank, --index-argv-by-rank

Uniquely index argv[0] for each process using its rank.

-max-restarts, --max-restarts<num>

Max number of times to restart a failed process.

--ppr <list>

Comma-separatedlist of number of processes on a given resource type [default: none].

-report-child-jobs-separately, --report-child-jobs-separately

Return the exit statusof the primary job only.

-report-events, --report-events <URI>

Report eventsto a tool listening at the specified URI.

-report-pid, --report-pid <channel>

Print out prun’s PID during startup. The channel must be either a ’-’ to indicatethat the pid is to be output to stdout, a ’+’ to indicate that the pid isto be output to stderr, or a filename to which the pid is to be written.

-report-uri, --report-uri <channel>

Print out prun’s URI during startup. The channelmust be either a ’-’ to indicate that the URI is to be output to stdout, a’+’ to indicate that the URI is to be output to stderr, or a filename towhich the URI is to be written.

-show-progress, --show-progress

Output a briefperiodic report on launch progress.

-terminate, --terminate

Terminate theDVM.

-use-hwthread-cpus, --use-hwthread-cpus

Use hardware threads as independentcpus.

-use-regexp, --use-regexp

Use regular expressions for launch.

Thefollowing options are useful for developers; they are not generally usefulto most users:

-d, --debug-devel

Enable debugging. This is not generally usefulfor most users.

-display-devel-allocation, --display-devel-allocation

Displaya detailed list of the allocation being used by this job.

-display-devel-map,--display-devel-map

Display a more detailed table showing the mapped locationof each process prior to launch.

-display-diffable-map, --display-diffable-map

Display a diffable process map just before launch.

-display-topo, --display-topo

Display the topology as part of the process map just before launch.

--report-state-on-timeout

When paired with the --timeout command line option, report the run-time subsystemstate of each process when the timeout expires.

There may be other optionslisted with prun --help.

Description

One invocation of prun starts anapplication running under PSRVR. If the application is single process multipledata (SPMD), the application can be specified on the prun command line.

If the application is multiple instruction multiple data (MIMD), comprisingof multiple programs, the set of programs and argument can be specifiedin one of two ways: Extended Command Line Arguments, and Application Context.

An application context describes the MIMD program set including all argumentsin a separate file. This file essentially contains multiple prun commandlines, less the command name itself. The ability to specify different optionsfor different instantiations of a program is another reason to use an applicationcontext.

Extended command line arguments allow for the description of theapplication layout on the command line using colons (:) to separate thespecification of programs and arguments. Some options are globally set acrossall specified programs (e.g. --hostfile), while others are specific to a singleprogram (e.g. -np).

Specifying Host Nodes

Host nodes can be identified onthe prun command line with the -host option or in a hostfile.

For example,

prun -H aa,aa,bb ./a.out

launches two processes on node aa and one on bb.

Or, consider the hostfile

% cat myhostfile
aa slots=2
bb slots=2
cc slots=2

Here, we list both the host names (aa, bb, and cc) but also how many'slots' there are for each. Slots indicate how many processes can potentiallyexecute on a node. For best performance, the number of slots may be chosento be the number of cores on the node or the number of processor sockets. If the hostfile does not provide slots information, PSRVR will attemptto discover the number of cores (or hwthreads, if the use-hwthreads-as-cpusoption is set) and set the number of slots to that value. This default behavioralso occurs when specifying the -host option with a single hostname. Thus,the command

prun -H aa ./a.out

launches a number of processes equal to thenumber of cores on node aa.

prun -hostfile myhostfile ./a.out

will launchtwo processes on each of the three nodes.

prun -hostfile myhostfile -hostaa ./a.out

will launch two processes, both on node aa.

prun -hostfile myhostfile-host dd ./a.out

will find no hosts to run on and abort with an error. Thatis, the specified host dd is not in the specified hostfile.

When runningunder resource managers (e.g., SLURM, Torque, etc.), PSRVR will obtain boththe hostnames and the number of slots directly from the resource manger.

Specifying Number of Processes

As we have just seen, the number of processesto run can be set using the hostfile. Other mechanisms exist.

The numberof processes launched can be specified as a multiple of the number of nodesor processor sockets available. For example,

prun -H aa,bb -npersocket 2./a.out

launches processes 0-3 on node aa and process 4-7 on node bb, whereaa and bb are both dual-socket nodes. The -npersocket option also turns onthe -bind-to-socket option, which is discussed in a later section.

prun -Haa,bb -npernode 2 ./a.out

launches processes 0-1 on node aa and processes 2-3on node bb.

prun -H aa,bb -npernode 1 ./a.out

launches one process per hostnode.

prun -H aa,bb -pernode ./a.out

is the same as -npernode 1.

Another alternativeis to specify the number of processes with the -np option. Consider nowthe hostfile

% cat myhostfile
aa slots=4
bb slots=4
cc slots=4

Now,

prun -hostfile myhostfile -np 6 ./a.out

will launch processes 0-3 onnode aa and processes 4-5 on node bb. The remaining slots in the hostfilewill not be used since the -np option indicated that only 6 processes shouldbe launched.

Mapping Processes to Nodes: Using Policies

The examples aboveillustrate the default mapping of process processes to nodes. This mappingcan also be controlled with various prun options that describe mappingpolicies.

Consider the same hostfile as above, again with -np 6:

node aa node bb node cc

prun 0 1 2 3 4 5

prun --map-by node 0 3 1 4 2 5

prun -nolocal 0 1 2 3 4 5

The --map-by node option will load balance the processes across the availablenodes, numbering each process in a round-robin fashion.

The -nolocal optionprevents any processes from being mapped onto the local host (in this casenode aa). While prun typically consumes few system resources, -nolocal canbe helpful for launching very large jobs where prun may actually need touse noticeable amounts of memory and/or processing time.

Just as -np canspecify fewer processes than there are slots, it can also oversubscribethe slots. For example, with the same hostfile:

prun -hostfile myhostfile-np 14 ./a.out

will launch processes 0-3 on node aa, 4-7 on bb, and 8-11 on cc. It will then add the remaining two processes to whichever nodes it chooses.

One can also specify limits to oversubscription. For example, with thesame hostfile:

prun -hostfile myhostfile -np 14 -nooversubscribe ./a.out

willproduce an error since -nooversubscribe prevents oversubscription.

Limitsto oversubscription can also be specified in the hostfile itself: % catmyhostfile
aa slots=4 max_slots=4
bb max_slots=4
cc slots=4

The max_slots field specifies such a limit. When it does, the slots valuedefaults to the limit. Now:

prun -hostfile myhostfile -np 14 ./a.out

causesthe first 12 processes to be launched as before, but the remaining twoprocesses will be forced onto node cc. The other two nodes are protectedby the hostfile against oversubscription by this job.

Using the --nooversubscribeoption can be helpful since PSRVR currently does not get 'max_slots' valuesfrom the resource manager.

Of course, -np can also be used with the -H or-host option. For example,

prun -H aa,bb -np 8 ./a.out

launches 8 processes. Since only two hosts are specified, after the first two processes aremapped, one to aa and one to bb, the remaining processes oversubscribethe specified hosts.

And here is a MIMD example:

prun -H aa -np 1 hostname: -H bb,cc -np 2 uptime

will launch process 0 running hostname on node aaand processes 1 and 2 each running uptime on nodes bb and cc, respectively.

Mapping, Ranking, and Binding: Oh My!

PSRVR employs a three-phase procedurefor assigning process locations and ranks:

mapping

Assigns a default locationto each process

ranking

Assigns a rank value to each process

binding

Constrains each process to run on specific processors

The mapping stepis used to assign a default location to each process based on the mapperbeing employed. Mapping by slot, node, and sequentially results in the assignmentof the processes to the node level. In contrast, mapping by object, allowsthe mapper to assign the process to an actual object on each node.

Note:the location assigned to the process is independent of where it will bebound - the assignment is used solely as input to the binding algorithm.

The mapping of process processes to nodes can be defined not just withgeneral policies but also, if necessary, using arbitrary mappings thatcannot be described by a simple policy. One can use the 'sequential mapper,'which reads the hostfile line by line, assigning processes to nodes inwhatever order the hostfile specifies. Use the -pmca rmaps seq option. Forexample, using the same hostfile as before:

prun -hostfile myhostfile -pmcarmaps seq ./a.out

will launch three processes, one on each of nodes aa,bb, and cc, respectively. The slot counts don’t matter; one process is launchedper line on whatever node is listed on the line.

Another way to specifyarbitrary mappings is with a rankfile, which gives you detailed controlover process binding as well. Rankfiles are discussed below.

The secondphase focuses on the ranking of the process within the job. PSRVR separatesthis from the mapping procedure to allow more flexibility in the relativeplacement of processes. This is best illustrated by considering the followingtwo cases where we used the —map-by ppr:2:socket option:

node aa node bb

rank-by core 0 1 ! 2 3 4 5 ! 6 7

rank-by socket 0 2 ! 1 3 4 6 ! 5 7

rank-by socket:span 0 4 ! 1 5 2 6 ! 3 7

Ranking by core and by slot provide the identical result - a simple progressionof ranks across each node. Ranking by socket does a round-robin ranking withineach node until all processes have been assigned a rank, and then progressesto the next node. Adding the span modifier to the ranking directive causesthe ranking algorithm to treat the entire allocation as a single entity- thus, the MCW ranks are assigned across all sockets before circling backaround to the beginning.

The binding phase actually binds each processto a given set of processors. This can improve performance if the operatingsystem is placing processes suboptimally. For example, it might oversubscribesome multi-core processor sockets, leaving other sockets idle; this canlead processes to contend unnecessarily for common resources. Or, it mightspread processes out too widely; this can be suboptimal if applicationperformance is sensitive to interprocess communication costs. Binding canalso keep the operating system from migrating processes excessively, regardlessof how optimally those processes were placed to begin with.

The processorsto be used for binding can be identified in terms of topological groupings- e.g., binding to an l3cache will bind each process to all processors withinthe scope of a single L3 cache within their assigned location. Thus, ifa process is assigned by the mapper to a certain socket, then a —bind-tol3cache directive will cause the process to be bound to the processorsthat share a single L3 cache within that socket.

To help balance loads,the binding directive uses a round-robin method when binding to levels lowerthan used in the mapper. For example, consider the case where a job is mappedto the socket level, and then bound to core. Each socket will have multiplecores, so if multiple processes are mapped to a given socket, the bindingalgorithm will assign each process located to a socket to a unique corein a round-robin manner.

Alternatively, processes mapped by l2cache andthen bound to socket will simply be bound to all the processors in thesocket where they are located. In this manner, users can exert detailedcontrol over relative MCW rank location and binding.

Finally, --report-bindingscan be used to report bindings.

As an example, consider a node with twoprocessor sockets, each comprising four cores. We run prun with -np 4 --report-bindingsand the following additional options:

% prun ... --map-by core --bind-to core
[...] ... binding child [...,0] to cpus 0001
[...] ... binding child [...,1] to cpus 0002
[...] ... binding child [...,2] to cpus 0004
[...] ... binding child [...,3] to cpus 0008

% prun ... --map-by socket --bind-to socket
[...] ... binding child [...,0] to socket 0 cpus 000f
[...] ... binding child [...,1] to socket 1 cpus 00f0
[...] ... binding child [...,2] to socket 0 cpus 000f
[...] ... binding child [...,3] to socket 1 cpus 00f0

% prun ... --map-by core:PE=2 --bind-to core
[...] ... binding child [...,0] to cpus 0003
[...] ... binding child [...,1] to cpus 000c
[...] ... binding child [...,2] to cpus 0030
[...] ... binding child [...,3] to cpus 00c0

% prun ... --bind-to none

Here, --report-bindings shows the binding of each process as a mask. In thefirst case, the processes bind to successive cores as indicated by themasks 0001, 0002, 0004, and 0008. In the second case, processes bind toall cores on successive sockets as indicated by the masks 000f and 00f0.The processes cycle through the processor sockets in a round-robin fashionas many times as are needed. In the third case, the masks show us that2 cores have been bound per process. In the fourth case, binding is turnedoff and no bindings are reported.

PSRVR’s support for process binding dependson the underlying operating system. Therefore, certain process bindingoptions may not be available on every system.

Process binding can alsobe set with MCA parameters. Their usage is less convenient than that ofprun options. On the other hand, MCA parameters can be set not only on theprun command line, but alternatively in a system or user mca-params.conffile or as environment variables, as described in the MCA section below.Some examples include:

prun option MCA parameter key value

--map-by core rmaps_base_mapping_policy core
--map-by socket rmaps_base_mapping_policy socket
--rank-by core rmaps_base_ranking_policy core
--bind-to core hwloc_base_binding_policy core
--bind-to socket hwloc_base_binding_policy socket
--bind-to none hwloc_base_binding_policy none

Rankfiles

Rankfiles are text files that specify detailed informationabout how individual processes should be mapped to nodes, and to whichprocessor(s) they should be bound. Each line of a rankfile specifies thelocation of one process. The general form of each line in the rankfileis:

rank <N>=<hostname> slot=<slot list>

For example:

$ cat myrankfile
rank 0=aa slot=1:0-2
rank 1=bb slot=0:0,1
rank 2=cc slot=1-2
$ prun -H aa,bb,cc,dd -rf myrankfile ./a.out

Means that

Rank 0 runs on node aa, bound to logical socket 1, cores0-2.
Rank 1 runs on node bb, bound to logical socket 0, cores 0 and 1.
Rank 2 runs on node cc, bound to logical cores 1 and 2.

Rankfiles can alternatively be used to specify physical processor locations.In this case, the syntax is somewhat different. Sockets are no longer recognized,and the slot number given must be the number of the physical PU as mostOS’s do not assign a unique physical identifier to each core in the node.Thus, a proper physical rankfile looks something like the following:

$ cat myphysicalrankfile
rank 0=aa slot=1
rank 1=bb slot=8
rank 2=cc slot=6

This means that

Rank 0 will run on node aa, bound to the core thatcontains physical PU 1
Rank 1 will run on node bb, bound to the core that contains physicalPU 8
Rank 2 will run on node cc, bound to the core that contains physicalPU 6

Rankfiles are treated as logical by default, and the MCA parameter rmaps_rank_file_physicalmust be set to 1 to indicate that the rankfile is to be considered as physical.

The hostnames listed above are 'absolute,' meaning that actual resolveablehostnames are specified. However, hostnames can also be specified as 'relative,'meaning that they are specified in relation to an externally-specified listof hostnames (e.g., by prun’s --host argument, a hostfile, or a job scheduler).

The 'relative' specification is of the form '+n<X>', where X is an integerspecifying the Xth hostname in the set of all available hostnames, indexedfrom 0. For example:

$ cat myrankfile
rank 0=+n0 slot=1:0-2
rank 1=+n1 slot=0:0,1
rank 2=+n2 slot=1-2
$ prun -H aa,bb,cc,dd -rf myrankfile ./a.out

All socket/core slot locations are be specified as logical indexes. Youcan use tools such as HWLOC’s 'lstopo' to find the logical indexes of socketand cores.

Application Context or Executable Program?

To distinguish thetwo different forms, prun looks on the command line for --app option. Ifit is specified, then the file named on the command line is assumed tobe an application context. If it is not specified, then the file is assumedto be an executable program.

Locating Files

If no relative or absolutepath is specified for a file, prun will first look for files by searchingthe directories specified by the --path option. If there is no --path optionset or if the file is not found at the --path location, then prun will searchthe user’s PATH environment variable as defined on the source node(s).

Ifa relative directory is specified, it must be relative to the initial workingdirectory determined by the specific starter used. For example when usingthe rsh or ssh starters, the initial directory is $HOME by default. Otherstarters may set the initial directory to the current working directoryfrom the invocation of prun.

Current Working Directory

The -wdir prunoption (and its synonym, -wd) allows the user to change to an arbitrarydirectory before the program is invoked. It can also be used in applicationcontext files to specify working directories on specific nodes and/or forspecific applications.

If the -wdir option appears both in a context fileand on the command line, the context file directory will override the commandline value.

If the -wdir option is specified, prun will attempt to changeto the specified directory on all of the remote nodes. If this fails, prunwill abort.

If the -wdir option is not specified, prun will send the directoryname where prun was invoked to each of the remote nodes. The remote nodeswill try to change to that directory. If they are unable (e.g., if the directorydoes not exist on that node), then prun will use the default directorydetermined by the starter.

All directory changing occurs before the user’sprogram is invoked.

Standard I/O

PSRVR directs UNIX standard input to/dev/null on all processes except the rank 0 process. The rank 0 processinherits standard input from prun. Note: The node that invoked prun neednot be the same as the node where the rank 0 process resides. PSRVR handlesthe redirection of prun’s standard input to the rank 0 process.

PSRVR directsUNIX standard output and error from remote nodes to the node that invokedprun and prints it on the standard output/error of prun. Local processesinherit the standard output/error of prun and transfer to it directly.

Thusit is possible to redirect standard I/O for applications by using the typicalshell redirection procedure on prun.

% prun -np 2 my_app < my_input> my_output

Note that in this example only the rank 0 process will receive the streamfrom my_input on stdin. The stdin on all the other nodes will be tied to/dev/null. However, the stdout from all nodes will be collected into themy_output file.

Signal Propagation

When prun receives a SIGTERM and SIGINT,it will attempt to kill the entire job by sending all processes in thejob a SIGTERM, waiting a small number of seconds, then sending all processesin the job a SIGKILL.

SIGUSR1 and SIGUSR2 signals received by prun arepropagated to all processes in the job.

A SIGTSTOP signal to prun willcause a SIGSTOP signal to be sent to all of the programs started by prunand likewise a SIGCONT signal to prun will cause a SIGCONT sent.

Othersignals are not currently propagated by prun.

Process Termination / SignalHandling

During the run of an application, if any process dies abnormally(either exiting before invoking PMIx_Finalize, or dying as the result ofa signal), prun will print out an error message and kill the rest of theapplication.

Process Environment

Processes in the application inherittheir environment from the PSRVR daemon upon the node on which they arerunning. The environment is typically inherited from the user’s shell. Onremote nodes, the exact environment is determined by the boot MCA moduleused. The rsh launch module, for example, uses either rsh/ssh to launchthe PSRVR daemon on remote nodes, and typically executes one or more ofthe user’s shell-setup files before launching the daemon. When running dynamicallylinked applications which require the LD_LIBRARY_PATH environment variableto be set, care must be taken to ensure that it is correctly set when bootingPSRVR.

See the 'Remote Execution' section for more details.

Remote Execution

PSRVR requires that the PATH environment variable be set to find executableson remote nodes (this is typically only necessary in rsh- or ssh-based environments-- batch/scheduled environments typically copy the current environment tothe execution of remote jobs, so if the current environment has PATH and/orLD_LIBRARY_PATH set properly, the remote nodes will also have it set properly). If PSRVR was compiled with shared library support, it may also be necessaryto have the LD_LIBRARY_PATH environment variable set on remote nodes aswell (especially to find the shared libraries required to run user applications).

However, it is not always desirable or possible to edit shell startup filesto set PATH and/or LD_LIBRARY_PATH. The --prefix option is provided for somesimple configurations where this is not possible.

The --prefix option takesa single argument: the base directory on the remote node where PSRVR isinstalled. PSRVR will use this directory to set the remote PATH and LD_LIBRARY_PATHbefore executing any user applications. This allows running jobs withouthaving pre-configured the PATH and LD_LIBRARY_PATH on the remote nodes.

PSRVRadds the basename of the current node’s 'bindir' (the directory where PSRVR’sexecutables are installed) to the prefix and uses that to set the PATHon the remote node. Similarly, PSRVR adds the basename of the current node’s'libdir' (the directory where PSRVR’s libraries are installed) to the prefixand uses that to set the LD_LIBRARY_PATH on the remote node. For example:

Local bindir:

/local/node/directory/bin

Local libdir:

/local/node/directory/lib64

If the following command line is used:

% prun --prefix /remote/node/directory

PSRVR will add '/remote/node/directory/bin' to the PATH and '/remote/node/directory/lib64'to the D_LIBRARY_PATH on the remote node before attempting to execute anything.

The --prefix option is not sufficient if the installation paths on the remotenode are different than the local node (e.g., if '/lib' is used on the localnode, but '/lib64' is used on the remote node), or if the installationpaths are something other than a subdirectory under a common prefix.

Notethat executing prun via an absolute pathname is equivalent to specifying--prefix without the last subdirectory in the absolute pathname to prun.For example:

% /usr/local/bin/prun ...

is equivalent to

% prun --prefix /usr/local

Exported Environment Variables

All environment variables that are namedin the form PMIX_* will automatically be exported to new processes on thelocal and remote nodes. Environmental parameters can also be set/forwardedto the new processes using the MCA parameter mca_base_env_list. While thesyntax of the -x option and MCA param allows the definition of new variables,note that the parser for these options are currently not very sophisticated- it does not even understand quoted values. Users are advised to set variablesin the environment and use the option to export them; not to define them.

Setting MCA Parameters

The -pmca switch allows the passing of parametersto various MCA (Modular Component Architecture) modules. MCA modules havedirect impact on programs because they allow tunable parameters to be setat run time (such as which BTL communication device driver to use, whatparameters to pass to that BTL, etc.).

The -pmca switch takes two arguments:<key> and <value>. The <key> argument generally specifies which MCA module willreceive the value. For example, the <key> 'btl' is used to select which BTLto be used for transporting messages. The <value> argument is the value thatis passed. For example:

prun -pmca btl tcp,self -np 1 foo

Tells PSRVR touse the 'tcp' and 'self' BTLs, and to run a single copy of 'foo' on anallocated node.

prun -pmca btl self -np 1 foo

Tells PSRVR to use the 'self'BTL, and to run a single copy of 'foo' on an allocated node.

No Hw-module Switch 1 Slot 1 Oversubscription Port-group 1

The -pmca switchcan be used multiple times to specify different <key> and/or <value> arguments. If the same <key> is specified more than once, the <value>s are concatenatedwith a comma (',') separating them.

Note that the -pmca switch is simplya shortcut for setting environment variables. The same effect may be accomplishedby setting corresponding environment variables before running prun. Theform of the environment variables that PSRVR sets is:

PMIX_MCA_<key>=<value>

Thus, the -pmca switch overrides any previously set environment variables. The -pmca settings similarly override MCA parameters set in the $OPAL_PREFIX/etc/psrvr-mca-params.confor $HOME/.psrvr/mca-params.conf file.

Unknown <key> arguments are still setas environment variable -- they are not checked (by prun) for correctness.Illegal or incorrect <value> arguments may or may not be reported -- it dependson the specific MCA module.

To find the available component types underthe MCA architecture, or to find the available parameters for a specificcomponent, use the pinfo command. See the pinfo(1) man page for detailedinformation on the command.

Setting MCA parameters and environment variablesfrom file.

The -tune command line option and its synonym -pmca mca_base_envar_file_prefixallows a user to set mca parameters and environment variables with thesyntax described below. This option requires a single file or list of filesseparated by ',' to follow.

A valid line in the file may contain zero ormany '-x', '-pmca', or “--pmca” arguments. The following patterns are supported:-pmca var val -pmca var 'val' -x var=val -x var. If any argument is duplicatedin the file, the last value read will be used.

MCA parameters and environmentspecified on the command line have higher precedence than variables specifiedin the file.

Running as root

The PSRVR team strongly advises againstexecuting prun as the root user. Applications should be run as regular (non-root)users.

Reflecting this advice, prun will refuse to run as root by default.To override this default, you can add the --allow-run-as-root option to theprun command line.

Exit status

There is no standard definition for whatprun should return as an exit status. After considerable discussion, wesettled on the following method for assigning the prun exit status (note:in the following description, the 'primary' job is the initial applicationstarted by prun - all jobs that are spawned by that job are designated 'secondary'jobs):

[bu]

if all processes in the primary job normally terminate withexit status 0, we return 0

[bu]

if one or more processes in the primaryjob normally terminate with non-zero exit status, we return the exit statusof the process with the lowest rank to have a non-zero status

[bu]

if allprocesses in the primary job normally terminate with exit status 0, andone or more processes in a secondary job normally terminate with non-zeroexit status, we (a) return the exit status of the process with the lowestrank in the lowest jobid to have a non-zero status, and (b) output a messagesummarizing the exit status of the primary and all secondary jobs.

[bu]

ifthe cmd line option --report-child-jobs-separately is set, we will return -only-the exit status of the primary job. Any non-zero exit status in secondaryjobs will be reported solely in a summary print statement.

By default,PSRVR records and notes that processes exited with non-zero terminationstatus. This is generally not considered an 'abnormal termination' - i.e.,PSRVR will not abort a job if one or more processes return a non-zero status.Instead, the default behavior simply reports the number of processes terminatingwith non-zero status upon completion of the job.

However, in some cases itcan be desirable to have the job abort when any process terminates withnon-zero status. For example, a non-PMIx job might detect a bad result froma calculation and want to abort, but doesn’t want to generate a core file.Or a PMIx job might continue past a call to PMIx_Finalize, but indicatethat all processes should abort due to some post-PMIx result.

It is not anticipatedthat this situation will occur frequently. However, in the interest of servingthe broader community, PSRVR now has a means for allowing users to directthat jobs be aborted upon any process exiting with non-zero status. Settingthe MCA parameter 'orte_abort_on_non_zero_status' to 1 will cause PSRVRto abort all processes once any process exits with non-zero status.

Terminations caused in this manner will be reported on the console asan 'abnormal termination', with the first process to so exit identifiedalong with its exit status.

Return Value

prun returns 0 if all processesstarted by prun exit after calling PMIx_Finalize. A non-zero value is returnedif an internal error occurred in prun, or one or more processes exitedbefore calling PMIx_Finalize. If an internal error occurred in prun, thecorresponding error code is returned. In the event that one or more processesexit before calling PMIx_Finalize, the return value of the rank of theprocess that prun first notices died before calling PMIx_Finalize willbe returned. Note that, in general, this will be the first process thatdied but is not guaranteed to be so.

If the --timeout command line optionis used and the timeout expires before the job completes (thereby forcingprun to kill the job) prun will return an exit status equivalent to thevalue of ETIMEDOUT (which is typically 110 on Linux and OS X systems).