On Thu, 10 Sep 2015, Tejun Heo wrote:
Why not just update node_data->node_zonelist in the first place?Also, shouldn't kmalloc_node() or any public allocator fall back
Also, what's the synchronization rule here? How are allocators
synchronized against node hot [un]plugs?
automatically to a near node w/o GFP_THISNODE? Why is this failing at
all? I get that cpu id -> node id mapping changing messes up the
locality but allocations shouldn't fail, right?
Yes that should occur in the absence of other constraints (mempolicies,
cpusets, cgroups, allocation type). If the constraints do not allow an
allocation then the allocation will fail.
Also: Are the zonelists setup the right way?