From: Michal Hocko <mhocko@kernel.org>
To: Christopher Lameter <cl@linux.com>
Cc: Johannes Thumshirn <jthumshirn@suse.de>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Damien Le Moal <damien.lemoal@wdc.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/6] mm: add kmalloc_array_node and kcalloc_node
Date: Wed, 27 Sep 2017 11:16:19 +0200 [thread overview]
Message-ID: <20170927091619.lkhfhwv3uu3km3sv@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.20.1709270358400.30866@nuc-kabylake>
On Wed 27-09-17 04:03:01, Cristopher Lameter wrote:
> On Wed, 27 Sep 2017, Michal Hocko wrote:
>
> > > Introduce a combination of the two above cases to have a NUMA-node aware
> > > version of kmalloc_array() and kcalloc().
> >
> > Yes, this is helpful. I am just wondering why we cannot have
> > kmalloc_array to call kmalloc_array_node with the local node as a
> > parameter. Maybe some sort of an optimization?
>
> Well the regular kmalloc without node is supposed to follow memory
> policies. An explicit mentioning of a node requires allocation from that
> node and will override memory allocation policies.
I see. Thanks for the clarification
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-09-27 9:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 8:20 [PATCH 0/6] Add kmalloc_array_node() and kcalloc_node() Johannes Thumshirn
2017-09-27 8:20 ` [PATCH 1/6] mm: add kmalloc_array_node and kcalloc_node Johannes Thumshirn
2017-09-27 8:42 ` Michal Hocko
2017-09-27 9:03 ` Christopher Lameter
2017-09-27 9:16 ` Michal Hocko [this message]
2017-09-27 8:56 ` Christopher Lameter
2017-09-29 12:00 ` Vlastimil Babka
2017-09-27 8:20 ` [PATCH 2/6] block: use kmalloc_array_node Johannes Thumshirn
2017-09-27 8:57 ` Christopher Lameter
2017-09-27 8:20 ` [PATCH 3/6] IB/qib: " Johannes Thumshirn
2017-09-27 8:58 ` Christopher Lameter
2017-09-27 8:20 ` [PATCH 4/6] IB/rdmavt: " Johannes Thumshirn
2017-09-27 9:04 ` Christopher Lameter
2017-09-27 8:20 ` [PATCH 5/6] mm, mempool: " Johannes Thumshirn
2017-09-27 9:04 ` Christopher Lameter
2017-09-27 8:20 ` [PATCH 6/6] rds: ib: " Johannes Thumshirn
2017-09-27 9:03 ` Christopher Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170927091619.lkhfhwv3uu3km3sv@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox