Re: [lc-devel] Re: [Openmosix-devel] oM + cc doesn't mixw

[Jordi <mu...@wa...>]

> Compressed swap is tied to compressed cache implementation, so porting
> it (without compressed caching) would require some work. BTW, when I
> implemented compressed swap, my focus was mostly swapping on disk,
> where the transfer rate isn't a critical matter. I was actually
> interested in reducing the number of IO operations, hence checking
> this compression impact on the performance. Given the initial design
> and implementation, I think there is much room for improvement in this
> code, if we came to the conclusion it may be worth adding this feature
> to openMosix.
>

It's a long time since i last read code of Openmosix or cc but at that time at 
least it was not difficult to mix both projects. Dealing with compressed 
pages is not more difficult that dealingg with swap space. 
The main problem i see is a philosofical problem.
Openmosix when tryingg to optimice CPU (load balancing processes accordiing to 
CPU usage) assumes that CPU must be optimize but net bandwidth and computer 
I/O is cheap and fast. So it's worthy to sacrify I/O to CPU.
mm-cc is assuming that CPUs doubles their power every 2 years but the rest of 
the computer components advance more slowly. So it's worthy to sacrify CPU to 
I/O.

I don't know  (as i'd make no test) what can happend missing both projects.
Missing both projects correctly seems a different project to me. Where yoou 
can specify if you want to optimize CPU and disk access but no networking or 
the other way round so it manage both openmosix and mm-cc to use more one 
resource or other one.

--
Jordi Polo