Messages in this thread | | | Date | Thu, 10 Sep 2015 18:08:57 -0400 | From | Tejun Heo <> | Subject | Re: [PATCH v2 3/7] x86, gfp: Cache best near node for memory allocation. |
| |
Hello,
On Thu, Sep 10, 2015 at 05:02:31PM -0500, Christoph Lameter wrote: > > Also, shouldn't kmalloc_node() or any public allocator fall back > > 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? > > Without a node specification allocations are subject to various > constraints and memory policies. It is not simply going to the next node. > The memory load may require spreading out the allocations over multiple > nodes, the app may have specified which nodes are to be used etc etc.
Yeah, sure, but even w/ node specified, it shouldn't fail unless THISNODE, right?
Thanks.
-- tejun
| |