|
Kernel mode of multi process
For some MMU system, the OS protecting mechanism can confirm the errors in user process not to interfere the whole system. But in Linux System, GUI is forced to run under C/S mode, which results in many extra process context switches, and IPC mechanism cannot provide efficient data copy, reducing the efficiency largely.
|
|
|
On XIPOS, XIPOS GUI uses special OS memory mechanism, which shares the memory same address. This reduces the costs of C/S mode, but some synchronous mechanisms must be added. Regarding the features of GUI application applied in embedded environment, what we get is bigger than what we lost, which has been certificated by fact. With the same hardware, the GUI application run under XIPOS mode is much more fluent than the one under C/S mode. Furthermore, in some hardware systems, synchronous mechanism can be optimized dramatically.
Resources occupied
- mips R3000 platform
- Code
- GUI system:100-200 Kbytes, according to deployment
- Data
- Global data:12-64 Kbytes, according to deployment
- Every user process:240 Bytes
- Every window: 140 Bytes on average, dynamically changing
Suitable hardware environment settings
XIPOS can run on 2M RAM hardware environment. If use XIP mode, RAM can be less than 1M, and XIPOS GUI can be configured to multi process mode.
XIPOS supports all kinds of display modes from monochrome to 24bits full color.
|
