On Fri, 16 Jun 2006 10:29:35 -0700
Ashok Raj <[email protected]> wrote:
> Should we have this flag on a per-task so we know if this task should be
> killed, or could be migrated without damage (assuming its going to run slow,
> but nothing critically bad will happen)
>
> Iam just worried if killing them globally without giving them a chance is
> any good and favorite apps such as databases will have probably have
> ill effects.
>
In the big servers which equips cpu-hotplug, apps should work as they designed.
If not, apps are already in buggy state.
IMHO, just stopping it is better than allowing execution in buggy state.
I used SIGSTOP. If a system admin or SIGCONT handler can modify cpu_allowed of
stopped thread, apps can go on. I think this is a realistic workaround.
(if the process is stopped, parent process of it can catch it by waitpid.)
p.s.
I think prefer cpu + allowed cpu will help this kind of probem, but there is no
interface..
-Kame
-
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]
