Re: OpenMosix and Checkpointing

>   This seems to becoming a often recently, with people assuming that
> because openMosix does migration it it can do check pointing. Would
> you mind enlightening me as to why that is.

It seems that, to migrate a process, you must transfer its state
(address space, register file, etc.) from one machine to another.  If
you can do that, it seems you could 'intercept' the transfer, and
save/restore that state to/from a file.  Of course, my understanding
of openMosix might be totally wrong (again, I've only just started to
look at it), so please correct me if I am, ad I want to understand it.

>
>  I would like to clear up one possible error in your impression of
> openMosix, there is no subset of features for HPC, that is all
> openMosix is about. If some wants any kind of HAC deployment openMosxi
> would be counter productive as a single node failure can bring make
> the whole cluster hiccup, and at the very least toats any jobs that
> where touching the failed node at time of failure.
>

The work I'm discussing is not HAC (e.g. automatic, transparent,
fail-over of a webserver, etc.) but rather providing fault-tolerance
for HPC applications, i.e., if an application fails 15 hours into a 30
hour run, we can (maybe after the whole cluster is rebooted) restart
the application from a saved checkpoint file and not have to re-do all
the lost work.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642