Cashmere Command Line Arguments

Cashmere: Command Line Arguments

Cashmere claims all command line argument following a ``--''. Arguments before the ``--'' should be processed by the user application.

For example, to start the application ``ufft'', you could give the following command line:

ufft -n 512 -- -p:5

``Ufft'' would process the command line arguments -n 512. Cashmere would precess the command line argument -p:5.

Cashmere supports the following command line arguments:

-c:cpus: Sets the maximum number of compute processes (CPUs) that will be started on each node. If no -c: argument is given, all available processors will be used for either compute processes or protocol processes.
-n:nodes: Sets the maximum number of nodes that will be used to run the application. If no -n: argument is given, all nodes in the cluster will be used.
-p:processes: Sets the maximum number of compute processes that will be used to run the application. If no -p: argument is given, all available processors will be used subject to the limitations implied by any -c: or -n: arguments.
-i: Use inter-node interrupts for message notification. This option is currently not suppored on Cashmere-2L.
-l:file: Load home node assignments from the specified file. Assignment will hold for the entire execution run, i.e. no migration.
-o:file: At end of execution, output home node assignments to the specified file.
-m:bytes: Sets the maximum number of bytes of shared memory available to the application. If no argument is given, Cashmere will allocate 64MB of shared memory if the application does not use csm_init_memory_size to specify a memory size.
-d:debug_level: Sets the level of debugging information printed by the protocol library. The default is level 0, meaning no debugging information.

Note that numeric values for command line arguments may be given either in decimal or hexadecimal. If hexadecimal is used, the value must be prefixed with a ``0x''.