From: Christoph Lameter <cl@gentwo.org>
To: Pekka Enberg <penberg@fastmail.fm>
Cc: Pekka Enberg <penberg@kernel.org>, Joonsoo Kim <js1304@gmail.com>,
Glauber Costa <glommer@parallels.com>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: [3.12 1/3] Move kmallocXXX functions to common code
Date: Wed, 14 Aug 2013 16:39:06 +0000 [thread overview]
Message-ID: <000001407db1e7c4-40866f2d-32c7-470a-a81a-94db87cdafa7-000000@email.amazonses.com> (raw)
In-Reply-To: <520B9AB0.7010209@fastmail.fm>
On Wed, 14 Aug 2013, Pekka Enberg wrote:
> The introduction kmalloc_large() needs to happen in a
> separate patch. What exactly is the benefit of adding the
> new API, btw? Why don't people just use the page allocator
> directly?
The advantage of kmalloc_large is that is has the same calling convention
as kmalloc. get_free_pages() etc require page addresses and return
unsigned longs meaning that conversions are required.
kmalloc_large functionality is already in use by slob and slub and
therefore is easy to make commonly available.
--
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:[~2013-08-14 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813154940.741769876@linux.com>
2013-08-13 15:49 ` [3.12 2/3] slub: remove verify_mem_not_deleted() Christoph Lameter
2013-08-13 15:49 ` [3.12 1/3] Move kmallocXXX functions to common code Christoph Lameter
2013-08-14 14:54 ` Pekka Enberg
2013-08-14 15:28 ` Pekka Enberg
2013-08-14 16:40 ` Christoph Lameter
2013-08-14 16:37 ` Christoph Lameter
2013-08-14 14:56 ` Pekka Enberg
2013-08-14 16:39 ` Christoph Lameter [this message]
2013-08-13 15:59 ` [3.12 3/3] seq_file: Use kmalloc_large for page sized allocation Christoph 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=000001407db1e7c4-40866f2d-32c7-470a-a81a-94db87cdafa7-000000@email.amazonses.com \
--to=cl@gentwo.org \
--cc=glommer@parallels.com \
--cc=js1304@gmail.com \
--cc=linux-mm@kvack.org \
--cc=penberg@fastmail.fm \
--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