| 9 | 11 | 3) Configure Platform Configuration File and select the daemons to launch on every processor. A default configuration maps all manager daemons to a single processor (the one where executable repositories are available) while the rest have only the mandatory daemons: |
| 10 | 12 | * Manager Processor Daemons: hwman, swman, statsman, sync_master, swload, frontend, stats, bridge, exec |
| 11 | 13 | * Rest of Processor Daemons: swload, frontend, stats, bridge, exec, sync |
| 12 | | 3) Launch '''runph''' on every processor |
| 13 | | 4) You will see in the Manager Processor how hwman daemon automatically detects the network of processors. |
| 14 | | 5) Load and run your application normally from the Manager Processor cmdman shell (or from the GUI) |
| 15 | | 6) You can check with execinfo command the actual mapping and execution information of processes. |
| | 14 | |
| | 15 | 4) Launch '''runph''' on every processor |
| | 16 | |
| | 17 | 5) You will see in the Manager Processor how hwman daemon automatically detects the network of processors. |
| | 18 | |
| | 19 | 6) Load and run your application normally from the Manager Processor cmdman shell (or from the GUI) |
| | 20 | |
| | 21 | 7) You can check with execinfo command the actual mapping and execution information of processes. |
