Changes between Version 6 and Version 7 of PhalUserGuide

Timestamp:

11/07/08 14:16:03 (16 years ago)

Author:

ismael (IP: 62.57.188.40)

Comment:

--

PhalUserGuide

@@ -105 +105 @@
 {{{
 runph$: phpause wimax
+
 runph$: phrun wimax 1000
 }}}
@@ -112 +113 @@
 == Customizing your Platform ==
 
+P-HAL Linux launcher admits two configuration files as arguments which modify certain Platform parameters. In this section we describe how to configure such parameters and what implications do they have:
+
+'''Platform Configuration File''': This file has one mandatory section, ''[cpu_info]'', and N optional sections, ''[daemon]''. The second selects which daemons (and their path) will be launched by runph. You can add or remove them according to which daemons you need in your platform (see PhalManual). The CPU configuration section, has two fields:
+ * ''mips'': Capacity in MIPS of your computer.
+ * ''tslot'': Duration of the time slot, in microseconds.
+ 
+'''External Interfaces Configuration File''': This files has one section for each external TCP interface of your platform. Before creating a network of P-HAL platforms, you should be very familiar with the P-HAL Environment concepts as it compromises selecting which daemons will run every platform, which depends on your network architecture. The format of the file is a set of sections (''[xitf]'') with the following mandatory fields:
+ * ''id'': Identification of the interface (hexadecimal 16-bit integer). Not any value is accepted as it is used by daemons to discover the purpose of the interface. It must be one of the following:
+  * 0x1: Master Control Interface.
+  * 0x1n: n=[0..F], Slave Control Interface.
+  * 0xpq: p=[2..F],q=[0..F], Data Interfaces
+
 [[BR]]
 
@@ -117 +130 @@
 
 To get the best performance of your waveform, the following hints may be useful:
- * Compile your modules with highest optimization and specify your processor architecture, e.g.:
+ * Compile your modules with '''highest optimization''' and specify your processor architecture, e.g.:
  {{{
  gcc -O3 -march=native -mfpmath=sse
@@ -123 +136 @@
  if you have a pentium/athlon processor with sse extensions.
 
- * Disable statistics or logs. These services may use a certain amount of CPU and bandwidth resources, disabling them may increase global performance. You can do that entering the following command in the P-HAL console:
+ * '''Disable statistics or logs'''. These services may use a certain amount of CPU and bandwidth resources, disabling them may increase global performance. You can do that entering the following command in the P-HAL console:
  {{{
  runph$: hwcmd stats_off
@@ -130 +143 @@
  You can re-enable them substituting 'off' by 'on'.
 
- * Run waveform processes with higher priority. Use the optional argument ''-p [priority]'' 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.
+ * Run waveform processes with '''higher priority'''. Use the optional argument ''-p [priority]'' 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.
 
- * 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 may be quite enough.
+ * '''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 may be quite enough.