This research paper is on the design methodology required to make intelligent decisions about the a new ERA AND APPRAOCH for MPSOC At Runtime using RTOS Algorithm. However we see that evidence of the soundness of the methodology by applying it on actual applications is a major requirement. This evolution, embedded processors become ubiquitous(present every where simultaneously) and a new role for embedded software in contemporary and future Multiple-Processor systems -on-Chip (MP-SoC) is reserved. Next to these programmable components, they contain a large number of memories organized in many different ways. Hence there is a need for proper management of all the data and computation in these complex systems.
[...] For example, the application is responsible for managing the assigned L2 memory block or to make sure data is copied in a timely fashion from its assigned L2 memory block to its assigned L1 memory block. Although the run-time 2 manager is responsible for handling the application's request for a memory block, the application itself is responsible for managing the allocation of memory resources within that block. This cooperation obviously requires special constructs within the MPSoC run-time manager. In addition, it should be possible to perform a Pareto point switch at run-time in order to react to a changing environment (e.g. [...]
[...] software in contemporary and future MultipleProcessor Systems-on-Chip (MP-SoC) is reserved Algorithm The following essential research problems need to be addressed to solve this problem: STEP I Massive parallelism is needed in order to reach to low power goals. This includes sub-word parallelism, instruction parallelism and coarse multi-processor parallelism. Especially the problem of using sub-word parallelism is not solved in both academia and industry. STEP It must be investigated how much of each type of parallelism needs to be exploited for the Ambient Intelligence application domain. [...]
[...] STEP The main question here deals with how to select a Pareto point in the Pareto hyper surface that minimizes the cost (according to some cost function) for a certain required performance and that considers the available platform resources. As the above figure illustrates, run-time management contains two major components: requirements management, dealing with Pareto point selection and Pareto point switching according to the user requirements and with the actual assignment of the resources. Hence, this raises the question of how the Pareto point selection and the resource assignment algorithm will be linked. [...]
[...] Optimized Design flows, Middleware and RTOS components will play a major role in addressing this challenge. STEP-V There is a need to create a run-time management glue layer that is perfectly suited for the MPSoC environment. This component illustrates how an MPSoCspecific run-time management layer is able to alleviate the needs of the MPSoC environment. The (design time) exploration and optimization component starts out by analyzing and profiling the target application together with a set of potential platform properties (e.g. [...]
using our reader.