Re: [PATCH x86_64] Live Patching Function on 2.6.11.7

[Kyle Moffett <mrmacman_g4@mac.com>]

On Apr 25, 2005, at 21:34, Takashi Ikebe wrote:
> Valdis.Kletnieks@vt.edu wrote:
> > When asked "Why don't you just reboot the affected switches?" his
> > response was "This assumes that the switch had ever been booted in
> > the first place". (Apparently, the *whole thing* had been
> > on-the-fly replaced/patched without an actual reload happening...)
> > Gaaahhh! :)
>
> I think that's the common sense in every carrier.

That is definitely not common sense.  It may be good business
practice, but those are two *entirely* different things.

> If we reboot the switch, the service will be disrupted.

Yes.  My personal favorite solution to this problem is HeartBeat,
some Open-Source software that is very good at maintaining high
availability.  With a properly written multi-system clustering
switch application that utilizes the Linux Virtual-Server tools,
you could reasonably efficiently run a system such that you can
reboot any individual system without any loss of service.

> The phone network is lifeline, and does not allow to be disrupt
> by just bug fix.  I think same kind of function is needed in many
> real enterprise/mission-critical/business area.

But you miss the point.  Linux is *NOT* about "business", or
"enterprise", or "mission-critical".  Linux is (at least to
many hackers) about hacking, having fun, and Good Design(TM).

> All do with ptrace may affect target process's time critical
> task. (need to stop target process whenever fix)

So don't do it with ptrace!!! I've given you one other method
that uses minimal changes to existing software and emulates the
crappy mmap3 call you keep trying to push.

> All implement in user application costs too much,

What about one of the dozen other offered methods?

> need to implement all the application...

So why not write a utility library?  You'd need to "implement
all in the kernel", too, and since it can be done better in
userspace, let's keep out the bloat while we're at it.

> (and I do not know this approach really works on time critical
> applications yet.)

So test it! You're clearly working for a big corporation with
the money and resources to develop something like this, so do
so, and if you get something that works well, *and* uses good
design, we'll welcome patches!

> There are clear demand to realize this common and GPL-ed
> function....

The kernel is not about business, demand, or what the CEO of
some big-name company wants.  The kernel strives for the goal
of "Good Engineering (TM)".


Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/