On Fri, 23 Jun 2006 09:27:46 -0500
Nathan Lynch <[email protected]> wrote:
> KAMEZAWA Hiroyuki wrote:
> > This patch adds sysctl cpu_removal_migration.
> > If cpu_removal_migration == 1, all tasks are migrated by force.
> > If cpu_removal_migration == 0, cpu_hotremoval can fail because of not-migratable
> > tasks.
> >
> > Note: cpu scheduler's notifier chain has the highest priority. then, this
> > failure detection will be done at first.
>
> I'm still not convinced that this is a good thing to do. I reiterate:
> this can be implemented in userspace (probably with fewer lines of
> code, even). Why should this policy be in the kernel?
>
I don't think so.
If we can expect all things can be maintained by user-space in proper way,
why we need forced migration ? This patch is just one of possible workarounds.
and implemtns, "success always" and "fail if busy" policy to cpu-hot-remove.
-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]
