From their website:
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.
It seems that this implementation would boost considerably the performance (they claim):
An improvement of 62% for asynchronous display or 384% for synchronous display of images of a 100x100 size.
Scrolling a web page under MicroXwin is much faster and smoother.
There are only about 300 Kbytes of kernel memory in use by the kernel module. X.Org server, however, has a run-time memory usage of 12MB.
The smallest MicroXwin distribution can fit within 1 megabyte of disk space in contrast to the X.Org Server, which has a disk footprint of 1.8MB.
What I don't understand is: it seems all good and perfect, but apart from the fact that is a proprietary module, what are the big cons?
I mean if a distribution is going to use it, what would be the limitations for a Home user? (3D and 2D missing funcionality, or impossibility to use some open or closed drivers etc etc, application incompatibility?)
Is out there any distribution implementing that?
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.
It seems that this implementation would boost considerably the performance (they claim):
An improvement of 62% for asynchronous display or 384% for synchronous display of images of a 100x100 size.
Scrolling a web page under MicroXwin is much faster and smoother.
There are only about 300 Kbytes of kernel memory in use by the kernel module. X.Org server, however, has a run-time memory usage of 12MB.
The smallest MicroXwin distribution can fit within 1 megabyte of disk space in contrast to the X.Org Server, which has a disk footprint of 1.8MB.
What I don't understand is: it seems all good and perfect, but apart from the fact that is a proprietary module, what are the big cons?
I mean if a distribution is going to use it, what would be the limitations for a Home user? (3D and 2D missing funcionality, or impossibility to use some open or closed drivers etc etc, application incompatibility?)
Is out there any distribution implementing that?
Comment