MicroXwin 一个优化的 X Window Systems
2008-12-13 00:37
148 查看
转载时请注明出处和作者联系方式:http://blog.csdn.net/mimepp
作者联系方式:YU TAO <yut616 at sohu dot com>
看到一个 MicroXwin 系统,架构很适合嵌入系统,这里做个记录。
http://www.microxwin.com 国内好象不能直接访问,需要找些代理,或其他工具来访问。
MicroXwin implements graphics processing in the kernel as a
load module and provides a character driver interface to the associated X11
library.
MicroXwin is binary compatible to the Xlib API.
However it is neither client server nor network oriented. Graphics operations are implemented in
the linux kernel via a kernel module.
An open source Xlib library sends graphics commands to the kernel.
There is no network overhead and no context switch from X client to X server.
This makes our solution smaller and faster than traditional X Windows.
空间占用小:
The storage and run-time memory requirements for MicroXwin is much lower than Xorg server.
The sizes of the main compoenents for x86 are:
LibX11.so is 720K bytes.
LibXext.so is 7K bytes.
Kernel module x11.ko is 200K bytes.
The Xorg server has a disk footprint of 1.8MB with run time memory usage of 12MB.
This is much higher than the roughly 300Kbytes of kernel memory used by the kernel module.
Besides that MicroXwin does all bitmap rendering in the kernel and needs only a small set
of SNF fonts. The smallest MicroXwin distribution can fit within ~ 1MB of disk space.
不过商用有 license 问题。
作者联系方式:YU TAO <yut616 at sohu dot com>
看到一个 MicroXwin 系统,架构很适合嵌入系统,这里做个记录。
http://www.microxwin.com 国内好象不能直接访问,需要找些代理,或其他工具来访问。
MicroXwin implements graphics processing in the kernel as a
load module and provides a character driver interface to the associated X11
library.
MicroXwin is binary compatible to the Xlib API.
However it is neither client server nor network oriented. Graphics operations are implemented in
the linux kernel via a kernel module.
An open source Xlib library sends graphics commands to the kernel.
There is no network overhead and no context switch from X client to X server.
This makes our solution smaller and faster than traditional X Windows.
空间占用小:
The storage and run-time memory requirements for MicroXwin is much lower than Xorg server.
The sizes of the main compoenents for x86 are:
LibX11.so is 720K bytes.
LibXext.so is 7K bytes.
Kernel module x11.ko is 200K bytes.
The Xorg server has a disk footprint of 1.8MB with run time memory usage of 12MB.
This is much higher than the roughly 300Kbytes of kernel memory used by the kernel module.
Besides that MicroXwin does all bitmap rendering in the kernel and needs only a small set
of SNF fonts. The smallest MicroXwin distribution can fit within ~ 1MB of disk space.
不过商用有 license 问题。
相关文章推荐
- MicroXwin 一个优化的 X Window Systems
- 关于数据库查询优化的一个例子(责任中心例子)
- 一个容易被大家忽略的多线程性能优化方案:Cache行级别优化
- 一个优化分析的例子
- chrome下form和a标签弹出新window,而不是打开一个新的tab
- Sql 一个SQL语句的优化
- Linux 3.6版本内核后关于路由cache的一个优化
- mysql通过“延迟关联”进行limit分页查询优化的一个实例
- SetForegroundWindow、SetActiveWindow、SetFocus 如何将一个某个窗口提到最顶层
- 转载_一个 SPI 转串口驱动的优化
- 一个window机器上配置多个tomcat
- 一个Web报表项目的性能分析和优化实践(七):性能监测工具JavaMelody
- 一个供查询用的datawindow
- 分享群内见到的一个引索优化案例
- Window Service 创建:在后台执行一个服务,可定时做一些操作,如轮询数据库,定时发邮件
- 一个矩阵乘法优化期望dp的题
- popupwindow弹出后出现当前activity和前一个activity一起出现的状况(window透明的设置)
- 在一个DataWindow中修改多个Table
- js 打开一个新页面 window.open()
- 一步步做程序优化-讲一个用于OpenACC优化的程序(转载)