Changes between Version 3 and Version 4 of DsxDocumentation

Timestamp:

Jan 27, 2008, 7:10:37 PM (16 years ago)

Author:

alain

Comment:

--

DsxDocumentation

@@ -3 +3 @@
 [[PageOutline]]
 
-== A) Goals ==
+== A) Goals and general principles ==
 
 DSX stands for ''Design Space eXplorer''. It helps the system designer to map a multi-threaded software application
 on a multi-processor hardware architecture (MP-SoC) modeled with the SoCLib components.
 
-It supports the hardware software codesign approach, and allows the designer to define successively :
- * the hardware architecture : number of processors, number of memory banks, peripherals, etc.
- * the software application structure : Task & Communication Graph
+It supports the hardware software codesign approach, allowing the designer to define successively :
+ * 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
 
@@ -25 +25 @@
 both the performances and the power consumption. 
 
-== B) General Principles ==
-
 The general principles are the following:
  * The coarse grain parallelism is 
@@ -32 +30 @@
  * 
  * [https://www-asim.lip6.fr/trac/mutekh Mutek] : OS kernel for embedded MPSoCs
-
-=== B1)  System Resources Layer ===
-
-We want to map the multi-threaded software application on several hardware platforms,
-without any modification of the task code. One important platform is a POSIX compliant
-workstation, as we want to validate the multi-threaded software application on a 
-workstation before starting the mapping on the MPSoC architecture.
-
-DSX defines a '''system Ressource Layer''' API (SRL), that is an abstraction of the synchronization
-and communication services provided by the various target platforms. The SRL API helps
-the programmer to distinguish the embedded application code from the system code used for
-inter-tasks communications and synchronizations.
-
-Three  platforms are supported :
- * Any Linux (or Unix)  workstation  supporting the POSIX threads,
- * MP-SoC architecture using the MUTEK/D operation system,
- * MP-SoC architecture using the MUTEK/S operating system,
-
-MUTEK/D is an embedded, POSIX compliant, distributed,  operating system for MP-SoCs, 
-while MUTEK/S is an optimized version: the performances are improved, and the memory
-footprint is reduced, at the cost of loosing the POSIX compatibility. 
-
-=== B2)  DSX/L language ===
 
 DSX/L is a language based on PYTHON, that allows the system designer to describe :
@@ -65 +40 @@
 code that will be uploaded in the MP-Soc embedded memory. 
 
-== C)  Describing the software application ==
+== B)  System Resources Layer ==
 
-== D)  Describing the hardware architecture ==
+We want to map the multi-threaded software application on several hardware platforms,
+without any modification of the task code. One important platform is a POSIX compliant
+workstation, as we want to validate the multi-threaded software application on a 
+workstation before starting the mapping on the MPSoC architecture.
+
+DSX defines a '''system Ressource Layer''' API (SRL), that is an abstraction of the synchronization
+and communication services provided by the various target platforms. The SRL API helps
+the C programmer to distinguish the embedded application code from the system code used for
+inter-tasks communications and synchronizations.
+
+ * Communications : blocking & non-blocking Read & Write access to a MWMR channel
+{{{
+void srl_mwmr_read( srl_mwmr_t, void * , size_t ) ;
+void srl_mwmr_write( srl_mwmr_t, void * , size_t ) ;
+
+size_t srl_mwmr_try_read( srl_mwmr_t, void * , size_t ) ;
+size_t srl_mwmr_try_write( srl_mwmr_t, void * , size_t ) ;
+
+void srl_mwmr_flush( srl_mwmr_t ) ;
+}}}
+ * Synchronization barrier
+{{{
+void srl_barrier_wait( srl_barrier_t ) ;
+}}}
+ * taking and releasing a lock 
+{{{
+srl_loock_lock( srl_lock_t ) ;
+srl_lock_unlock( srl_lock_t ) ;
+}}}
+* accessing a shared memory space (address and size)
+{{{
+void* srl_memspace_addr( srl_memspace_t ) ;
+size_t srl_memspace_size( srl_memspace_t ) ;
+}}}
+
+Three  platforms are presently supported :
+ * Any Linux (or Unix)  workstation  supporting the POSIX threads,
+ * MP-SoC architecture using the MUTEK/D operation system,
+ * MP-SoC architecture using the MUTEK/S operating system,
+
+MUTEK/D is an embedded, POSIX compliant, distributed,  operating system for MP-SoCs, 
+while MUTEK/S is an optimized version: the performances are improved, and the memory
+footprint is reduced, at the cost of loosing the POSIX compatibility. 
+
+== C)  Defining the software application ==
+
+== D)  Defining the hardware architecture ==
 
 == E)  Mapping the software on the hardware ==