On 01/17/2017 10:07 PM, Mel Gorman wrote: > On Tue, Jan 17, 2017 at 08:20:08PM +0000, Mel Gorman wrote: > > I later recalled that we looked at this before and didn't think a reinit > was necessary because the location of cpuset_current_mems_allowed doesn't > change so I came back and took another look. The location doesn't change > but after the first attempt, we reset ac.nodemask to the given nodemask and > don't recheck current_mems_allowed if the cpuset changed. The application > of memory policies versus cpusets is a mess so it'll take time to pick > apart to see if this is even remotely in the right direction.
Yes, I spent most of last 2 days untangling this, so I'll post at least some RFC soon.
