Re: [patch] mm, oom: header nodemask is NULL when cpusets are disabled

2017-01-24 Thread Michal Hocko
On Thu 19-01-17 14:57:36, David Rientjes wrote: > Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly > sets the allocation nodemask to cpuset_current_mems_allowed when there is > no effective mempolicy. cpuset_current_mems_allowed is only effective > when cpusets are enabl

Re: [patch] mm, oom: header nodemask is NULL when cpusets are disabled

2017-01-20 Thread David Rientjes
On Fri, 20 Jan 2017, Vlastimil Babka wrote: > Could we simplify both patches with something like this? > Although the sizeof("null") is not the nicest thing, because it relies on > knowledge > that pointer() in lib/vsprintf.c uses this string. Maybe Rasmus has some > better idea? > > Thanks, >

Re: [patch] mm, oom: header nodemask is NULL when cpusets are disabled

2017-01-20 Thread Vlastimil Babka
On 01/19/2017 11:57 PM, David Rientjes wrote: > Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly > sets the allocation nodemask to cpuset_current_mems_allowed when there is > no effective mempolicy. cpuset_current_mems_allowed is only effective > when cpusets are enabled

Re: [patch] mm, oom: header nodemask is NULL when cpusets are disabled

2017-01-19 Thread Hillf Danton
On Friday, January 20, 2017 6:58 AM David Rientjes wrote: > > Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly > sets the allocation nodemask to cpuset_current_mems_allowed when there is > no effective mempolicy. cpuset_current_mems_allowed is only effective > when cpuset