Changes between Version 4 and Version 5 of DsxDocumentation

Timestamp:

Jan 27, 2008, 8:10:52 PM (17 years ago)

Author:

alain

Comment:

--

DsxDocumentation

@@ -9 +9 @@
 
 It supports the hardware software codesign approach, allowing the designer to define successively :
+ * the software application structure : number of tasks and communication channels
  * the hardware architecture : number of processors, number of memory banks, etc.
- * the software application structure : number of tasks and communication channels
- * the mapping of the software objects on the hardware components
+ * the mapping of the software application on the hardware architecture
 
-The software application must be statically defined as  a '''Task & Communications Graph'''.
-The number of tasks (defining the coarse grain parallelism), and the communication channels between
-tasks should not change during execution. The two targeted application domains are the telecommunication
-applications (where the tasks are handling packets or packet descriptors), and multi-media applications
-(where the tasks are handling audio or video streams).
-
-A specific goal of DSX is to allow the system designer to control not only the the placement of the 
-tasks on the processors, but also to control precisely the placement of the software objects (execution stacks,
+A specific goal of DSX is to allow the system designer to control not only the placement of the 
+tasks on the processors, but  the placement of the software objects (execution stacks,
 communication buffers, synchronization locks, etc.) on the memory banks. In shared memory multi-processors
 architectures with several physically distributed memory banks, such control is mandatory to optimize
 both the performances and the power consumption. 
 
-The general principles are the following:
- * The coarse grain parallelism is 
- * The software tasks are supposed to be written in C or C++.
- * 
- * [https://www-asim.lip6.fr/trac/mutekh Mutek] : OS kernel for embedded MPSoCs
+The two targeted application domains are the telecommunication applications (where the tasks are handling packets or packet descriptors), and multi-media applications (where the tasks are handling audio or video streams).
 
-DSX/L is a language based on PYTHON, that allows the system designer to describe :
- * the Task & Communication Graph (TCG)
- * the MP-SoC hardware architecture (using the hardware components available in SoCLib).
- * the mapping of the TCG on the MP-Soc architecture. 
+The general principles of the DSX tool are the following:
+ * The coarse grain parallelism of the software application must be statically defined as  a '''Task & Communications Graph (TCG)'''. The number of tasks, and the communication channels between tasks should not change during execution. 
+ * The software tasks are supposed to be written in C or C++, but - for portability reasons - the tasks must use an abstract '''System Resource Layer (SRL)''' API to access the communication and synchronizations resources. 
+ * Each task in the TCG can be implemented as a ''software task'' (software running on an embedded processor), or can be implemented as an ''hardware task'', (running as a dedicated hardware coprocessor).
+ * DSX allows the programmer to use unprotected shared memory spaces, but the prefered inter-tasks communication mechanism use the MWMR middleware. The MWMR (Multi-Writer, Multi-Reader) channels, are implemented as software FIFOs and can be shared by ''software tasks'', and by ''hardware tasks.
+* DSX provides classical synchronization mechanisms such as barriers and locks, but inter-task synchronisation is mainly done through the data availability in the MWMR channels.
+ * The target hardware architecture is a shared memory multi-processor system on chip (MP-SoC) using the SoCLib library of IP cores. But - in order to validate the multi-threaded software application - DSX is able to generate an executable binary code for a standard POSIX workstation.
+ * DSX supports the POSIX compliant [https://www-asim.lip6.fr/trac/mutekh Mutek]  OS kernel for embedded MPSoCs
+ * Finally, DSX defines the DSX/L language, based on PYTHON, that allows the system designer to describe in a single file the Task & Communication Graph (TCG), the MP-SoC hardware architecture, and various mapping of the TCG on the MP-Soc architecture. 
 
 The DSX/L script execution generates the binary code executable on the workstation, the 
@@ -71 +66 @@
 srl_lock_unlock( srl_lock_t ) ;
 }}}
-* accessing a shared memory space (address and size)
+ * accessing a shared memory space (address and size)
 {{{
 void* srl_memspace_addr( srl_memspace_t ) ;