Changes between Version 8 and Version 9 of ALOELinuxGuide
- Timestamp:
- 11/28/09 13:45:00 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ALOELinuxGuide
v8 v9 3 3 This section describes first steps on launching and running a waveform in ALOE for Linux. 4 4 If you plan to develop applications or you just want to learn more about ALOE, you should read the [wiki:WaveformDeveloperGuide Waveform Developer Guide]. 5 6 Here you will learn how to download a waveform from our repository (you will need a user/pwd to access) and launch it. You will also get familiar with most of ALOE commands.7 5 8 6 At this point we assume that you have downloaded and installed ALOE on your computer (see [wiki:PhalInstallGuide Install Guide]) and that your are familiar with Linux commands at user level. … … 12 10 == Launching ALOE == 13 11 14 If you downloaded ALOE from source, take a look at the 'example s' directory. There you will see the implementation of 3 ALOE objects (source, decimator and sink) and another folder called ''repository''. This directory is where Manager Daemons will look for configuration files, waveform definitions files and executables (and more things...). This path will be passed as the first argument to the ALOE launcher.12 If you downloaded ALOE from source, take a look at the 'example-repository' directory. This directory is where Manager Daemons will look for configuration files, waveform definitions files and executables (and so on). This path will be passed as the first argument to the ALOE launcher. 15 13 16 14 You will see that this directory has, among others, the following '''mandatory''' subdirectories: … … 30 28 runph 31 29 }}} 30 31 '''NOTE:''' To run ALOE at highest performance, it should be executed with root permissions. Simply launch it with sudo: 32 {{{ 33 sudo runph 34 }}} 35 32 36 33 37 [[BR]] … … 49 53 == Running a waveform: Basic ALOE commands == 50 54 51 ALOE can be controlled from a text console by typing commands. Basically, running a waveform compromises 3 steps: ''loading'', ''initializing'' and ''running''. You will do such by typing the appropriate commands in the input console. In the next example, we will load, initiali ze and run the example waveform.55 ALOE can be controlled from a text console by typing commands. Basically, running a waveform compromises 3 steps: ''loading'', ''initializing'' and ''running''. You will do such by typing the appropriate commands in the input console. In the next example, we will load, initialise and run the example waveform. 52 56 53 57 Once ALOE has been started (by default typing {{{ runph }}} from the source directory, we will load the waveform by typing in the prompt: … … 95 99 * ''name'': The name of the processor. 96 100 * ''mips'': Capacity in MIPS of your computer. 101 * ''nof_cores'': Number of SMP cores. 97 102 * ''tslot'': Duration of the time slot, in microseconds. 98 103 * ''run_as_daemon'': Run in background. … … 118 123 == Launching ALOE as a Daemon == 119 124 120 Running ALOE in background is often interesting when long time executions are going to be performed. In foreground executions, disconnecting user terminal (or ssh session) will kill ALOE processes. This can be prevented to happenif the user launches ALOE with the ''daemon'' option (as an argument or in the platform configuration file, see above) and appropriate selects an output file.125 Running ALOE in background is often interesting when long time executions are going to be performed. In foreground executions, disconnecting user terminal (or ssh session) will kill ALOE processes. This can be avoided if the user launches ALOE with the ''daemon'' option (as an argument or in the platform configuration file, see above) and appropriate selects an output file. 121 126 122 127 When running in this mode, '''CMDMANAGER''' daemon must be also launched as daemon as it can't read commands from standard input any more, and a tcp socket should be created for this purpose. Then, another CMDMANAGER process (local or remote) can connect to it and send normal ALOE commands (as if it was local). … … 168 173 if you have a pentium/athlon processor with sse extensions. 169 174 170 * Run waveform processes with '''higher priority'''. Run runph as root to set a lower kernel priority to your waveform processes. Normal kernel priorities are 0 and higher, if you choose lower priority for waveform processes, they will low with lower priority which may increase performance and/or time resolution. Use this option with caution, because if your component hangs (i.e. because of an infinite loop), any process would get scheduled, preventing it to be killed, which may totally freeze your computer.171 172 175 * '''Increase Kernel time resolution'''. Another measure you can adopt to achieve a higher performance can be increasing the kernel timer frequency. To do such you must recompile your kernel. How to do that is out of the scope of this document, however, if you use ''menuconfig'', the option you have to change is at '''Processor type and features->Timer frecuency'''. Setting that to 1000 Hz implies a resolution of 1ms which, with at 10ms slot duration should be enough. 173 176
