The central controller in [41] took significant time to execute the scheduling of 15 nodes, which had 109 control options, just to adapt CPU resource - memory configuration was not covered.
In the second example, as given in Fig. 7, the individual memory configurations are more distributed and not as close to the solution range borders as in the previous example.
All possible memory configurations were tested between on-chip and SDRAM memories in order to present the entire scope of possibilities running the three presented algorithms, including (or not) the use of the designed custom instruction, instead of the source GetCost function in every available Nios II processor (E, S, and F).
Contiki is designed for microcontrollers with small amounts of memory (a typical Contiki configuration is 2 kB of RAM and 40 kB of ROM).
Thus, at run-time, all these parameters need to be computed and loaded into the configuration memories when a new configuration is required.
It uses separate instruction and data cache memories and supports multiprocessor configurations: in particular, an SMP-aware configuration is well supported thanks to available memory management unit and snooping unit for cache coherence.
Dynamic reconfiguration during one frame duration is possible when the current configuration is small enough to load a new configuration in the memory.
Each instance's configuration is as follows: 1.7 GHz 2006 Intel Xeon processor, 1.7 GB memory, 160 GB storage.
For larger files, on the order of GBs for raw data, such configuration is not suitable, since this requires loading the full XML tree into memory.
The configuration is based on generating corresponding SystemC code containing the same tasks, processing and memory elements.
