Mutatis mutandis safe and predictable dynamic software updating josh gates ryder dating

by  |  18-May-2014 23:49

To take effect, these patches traditionally require either restarting system services, or often rebooting the machine. Sometimes this downtime can be scheduled, if for example the patch adds a feature, improves performance, etc.However, in some situations, such as applying a security patch, delaying the update is not desirable.There are several fundamental requirements in providing a dynamic update capability.

mutatis mutandis safe and predictable dynamic software updating-26

The rest of this paper is organised as follows: Section 2 discusses the system requirements for supporting dynamic update, Section 3 describes our implementation of dynamic update in K42, and Section 4 discusses how the same functionality might be implemented in other operating systems.

Next, Section 5 describes our experiences applying dynamic update to K42 using three motivating examples, Section 6 discusses the limitations of our implementation and our plans for future work, Section 7 compares related work, and Section 8 concludes.

They allow, for example, a new page replacement, file system, or network policy to be tested without rebooting.

Further, in more mature systems such as mainframes, some user constraints prevent the system from ever being shutdown.

The structure of the system dictates what is feasible.

Community Discussion