Re: [PATCH v3 0/5] CPU hotplug, cpusets: Fix issues with cpusetshandling during suspend/resume

[David Rientjes]

On Mon, 14 May 2012, Srivatsa S. Bhat wrote:

> Currently the kernel doesn't handle cpusets properly during suspend/resume.
> After a resume, all non-root cpusets end up having only 1 cpu (the boot cpu),
> causing massive performance degradation of workloads. One major user of cpusets
> is libvirt, which means that after a suspend/hibernation cycle, all VMs
> suddenly end up running terribly slow!
> 
> Also, the kernel moves the tasks from one cpuset to another during CPU hotplug
> in the suspend/resume path, leading to a task-management nightmare after
> resume.
> 

To deal with mempolicy rebinding when a cpuset changes, I made a change to 
mempolicies to store the user nodemask passed to set_mempolicy() or 
mbind() so the intention of the user could be preserved.  It seems like 
you should do the same thing for cpusets to store the "intended" set of 
cpus and respect that during cpu online?

> Patches 1 & 2 are cleanups that separate out hotplug handling so that we can
> implement different logic for different hotplug events (CPU/Mem
> online/offline). This also leads to some optimizations and more importantly
> prepares the ground for any further work dealing with cpusets during hotplug.
> 
> Patch 3 is a bug fix - it ensures that the tasks attached to the root cpuset
> see the updated cpus_allowed mask upon CPU hotplug.
> 
> Patches 4 and 5 implement the fix for cpusets handling during suspend/resume.

All of your patches are labeled to stable@xxxxxxxxxxxxxxx, but I seriously 
doubt any of this is stable material since it has been a long-standing 
issue (and perhaps intentional in some cases) and your series includes 
cleanups and optimizations that wouldn't be stable candidates, so I'd 
suggest removing that annotation.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/