Changes between Version 21 and Version 22 of projectstructure

Timestamp:

Jun 16, 2008, 4:43:01 PM (17 years ago)

Author:

fpecheux

Comment:

--

projectstructure

@@ -81 +81 @@
 
 Based on the online monitoring information that have been gathered by the appropriate monitoring resources (WP1), diagnosed and classified in the Architecture Instant Map Database AIM-DB (WP2) a collection of strategies for improving the application mapping are considered. This self-adaptability scheme may, depending on the system policy, aim at:
+[[BR]]
 *       Decreasing the system power consumption
 *       Ensuring real-time performance or more generally improving application performance
@@ -86 +87 @@
 
 These strategies operate on a task basis as per defined by the application task graph. Only the following on-line operations are considered:
-
+[[BR]]
 *       Migration. Tasks are moved from HW resource to HW resource for :
   *     Lowering communication cost / power consumption  in order to improve performance if an alternative processing resource has a more appropriate support for a particular task. Additionally, if some of the processing resources have time-sliced execution capabilities (a CPU running a multitasking operating system); migrating tasks results in a higher performance since time is shared among fewer tasks.
@@ -94 +95 @@
 
 *       Router reconfiguration. For either communication performance (avoiding contentions) or for dealing with a hardware defect on some units/physical links, the routing tables may be changed at run-time.
-
+[[BR]]
 The two first classes of operations may take place in different ways: 
 *       a fully centralized scenario where once the decision to remap the application has been taken, a global remapping is issued.