[lkml]   [2006]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] stop on cpu lost
    On Thu, 22 Jun 2006, Pavel Machek wrote:

    > > > Hm..
    > > > Then, there is several ways to manage this sitation.
    > > >
    > > > 1. migrate all even if it's not allowed by users
    > That's what I'd prefer... as swsusp uses cpu hotplug. All the other
    > options are bad... admin will probably not realize suspend involves
    > cpu unplugs..

    You probably first suspend a process? If a process was suspended by
    swsusp then we can just ignore the restriction because it will be
    returned later.

    The admin wants the system to behave in a consistent way. If he suddenly
    finds a process running on a cpu that was forbidden then that is weird
    and surprising to say the least and may go undetected for a long time.
    If the process gets killed when he disables the cpu then he will have to
    fix up his cpu restrictions.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-06-22 20:39    [W:0.020 / U:31.288 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site