There has been a discussion in comp.arch about making operating systems
hot-swappable. This does require deep design changes and it's very
unlikely that Linux will make these design changes just for being
hot-swappable. There are swappable parts in the kernel (modules), but
they all require to take that specific service down before swap.
The basic issue is that all kernel services must be state-less. Since a
lot of current OS services are all but stateless, they have to be
rewritten to store the state somewhere else. Basically, whenever
possible, move state to the application. When not possible (security
concerns, or performance problems), you need a self-describing
persistent structure of the data. The new kernel then can figure out how
to convert it to the new internal format.
Difficult? Nightmare!
-- Bernd Paysan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/