CE Requirements CE Requirements from a Supplier from a Supplier Perspective

CE Requirements CE Requirements from a Supplier from a Supplier Perspective
http://www.axe-inc.co.jp/pr/pdf/ce-ogrt-axe1.pdf
The Open Group Real-time & Embedded Systems Forum
2005/01/23 Shozo TAKEOKA AXE,Inc

QoS API for multimedia
- PVR (recording/playing runs at same time)
- Network protocol stack comsume large CPU power on receiving many packet
   and MPEG-Player works less frame rate
- ex: MPEG and Network, Video and Audio
- CPU-power-ratio must be changed dynamically

Consumer Electronics (advanced automobile device)
- no hard realtime requirement
- Linux, NetBSD, WinCE, T-Engine
- CPU power resource management is required.
- response time not recommended hardly in ordinary application.

highend mobile (mobile phone) need realtime
- in special CPU for communication, iTron, VxWorks
mobile phone's application processor not need realtime
- WebBrowser, Email, movie MPEG4)
- well user interaction.
- fast startup

required API for Multicore, SMP.
- multicore is not SMP.
SMP has cache coherency
some multicore hasn't cache coherency
- processing an I/O device by Multicore has some problem.
Synchronization: not useful the technique for SMP, cache is incoherent.
   holding the processing data on cache.


QoS API for multicore, SMP
malloc_mclass( int size, storage class)
onchip SRAM
on board offchip SRAM
ordinary DRAM
uncachable DRAM

Uncachable area used for holding mutexes on Multicore CPU.
Uncachable area is good for non-cahce-coherency-system.
Uncachable area can be used for DMA