On Fri, 23 Jun 2006, KAMEZAWA Hiroyuki wrote:
> Hm..
> Then, there is several ways to manage this sitation.
>
> 1. migrate all even if it's not allowed by users
If its not allowed then the system should not do this. Otherwise we get an
inconsistent system with lots of exceptions just because the user can
do something stupid.
> 2. kill mis-configured tasks.
If the user misconfigured then its their problem.
> 3. stop ...
That wont work well since the process may ignore stops. We have no history
of stopping processes. This would be new functionality to pioneer in
Linux.
> 4. cancel cpu-hot-removal.
>
> I just don't like "1".
> I discussed this problem with my colleagues before sending patch,
> one said "4" seems regular way but another said "4" is bad.
4 is a good thing. Just give the user some feedback as to why. F.e. write
a message to the syslog. This is the way we deal with many other
problem situations.
> I sent a patch for "4" in the first place but Andi Kleen said it's bad.
> As he said, I'm handling the problem for which I can't find a good answer :(
Andi: Why is 4 bad?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
