From: Christoph Lameter <cl@linux.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
David Rientjes <rientjes@google.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH] mm, slab: rename kmalloc-node cache to kmalloc-<size>
Date: Mon, 6 Feb 2017 08:55:37 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702060854330.27871@east.gentwo.org> (raw)
In-Reply-To: <20170206145238.GI2267@bombadil.infradead.org>
On Mon, 6 Feb 2017, Matthew Wilcox wrote:
> Could we lose the 'get_' from the front? I think 'kmalloc_cache_name()' is
> just as informative.
Hmmm.. Expose the static array in mm/slab.h instead? There may be other
cases in which the allocator specific code may need that information.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Lameter <cl@linux.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
David Rientjes <rientjes@google.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH] mm, slab: rename kmalloc-node cache to kmalloc-<size>
Date: Mon, 6 Feb 2017 08:55:37 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702060854330.27871@east.gentwo.org> (raw)
In-Reply-To: <20170206145238.GI2267@bombadil.infradead.org>
On Mon, 6 Feb 2017, Matthew Wilcox wrote:
> Could we lose the 'get_' from the front? I think 'kmalloc_cache_name()' is
> just as informative.
Hmmm.. Expose the static array in mm/slab.h instead? There may be other
cases in which the allocator specific code may need that information.
--
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-02-06 14:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 18:10 [PATCH] mm, slab: rename kmalloc-node cache to kmalloc-<size> Vlastimil Babka
2017-02-03 18:10 ` Vlastimil Babka
2017-02-04 2:26 ` kbuild test robot
2017-02-04 2:26 ` kbuild test robot
2017-02-04 8:27 ` Vlastimil Babka
2017-02-04 8:27 ` Vlastimil Babka
2017-02-06 14:47 ` Christoph Lameter
2017-02-06 14:47 ` Christoph Lameter
2017-02-06 14:52 ` Matthew Wilcox
2017-02-06 14:52 ` Matthew Wilcox
2017-02-06 14:55 ` Christoph Lameter [this message]
2017-02-06 14:55 ` Christoph Lameter
2017-02-07 17:15 ` kbuild test robot
2017-02-07 17:15 ` kbuild test robot
2017-02-07 21:38 ` Andrew Morton
2017-02-07 21:38 ` Andrew Morton
2017-02-08 9:12 ` Vlastimil Babka
2017-02-08 9:12 ` Vlastimil Babka
2017-02-08 9:26 ` Vlastimil Babka
2017-02-08 9:26 ` Vlastimil Babka
2017-02-08 15:13 ` Christoph Lameter
2017-02-08 15:13 ` Christoph Lameter
2017-02-08 21:54 ` Andrew Morton
2017-02-08 21:54 ` Andrew Morton
2017-02-09 9:12 ` Vlastimil Babka
2017-02-09 9:12 ` Vlastimil Babka
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=alpine.DEB.2.20.1702060854330.27871@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.