Re: [PATCH x86_64] Live Patching Function on 2.6.11.7

Chris Wedgwood
2005-04-18T07:56:55Z

On Mon, Apr 18, 2005 at 04:32:21PM +0900, Takashi Ikebe wrote:

> The software does not allow to stops over 100 milliseconds at worst
> case.

Out of interest, how do you ensure the process doesn't stop for that
long right now? Linux doesn't guarantee you'll get scheduled
(strictly speaking) in n milliseconds usually.

> Not to descent the service availability, software fix due to bug,
> should not stop the service, and live patching is very historical
> function in telecoms world.

Lots of really complicated and unnecessary things are common in the
telecoms world.

For the example you gave I can think of several ways to migrate data
to a new process (if need be) in a timely manner without interruption.
None of these *require* live patching.

> Every carrier, NEPs(Network Equipment Provider) provide/use this
> function to keep network service (such as telephone) available.

How does this *require* live patching?

> This function is very essential whenever the carrier use the linux
> as center of it's system.

Those are just marketing words.

> Therefore the live patching function should not stop the target
> process (service process) as possible as. the more times we stop the
> target process, the service goes unavailable...

Love patching seems like a very complicated thing to get right and it
could potentially blow up.

I'm guessing any suggestion of fixing the applications behavior would
be lost with some argument along the lines of: "this application was
written in 1824 by Ada Lovelace using pre-Roswell Alien Technology and
was certified NEBS compliant by the Deli Lama and god herself, so
clearly we can't touch a single line of it" or similar right?