From: Jamie Lokier <jamie@shareable.org>
To: Changli Gao <xiaosuo@gmail.com>
Cc: akpm@linux-foundation.org, Eric Dumazet <eric.dumazet@gmail.com>,
Jiri Slaby <jslaby@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Avi Kivity <avi@redhat.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [RFC] mm: generic adaptive large memory allocation APIs
Date: Thu, 6 May 2010 16:35:46 +0100 [thread overview]
Message-ID: <20100506153546.GC28512@shareable.org> (raw)
In-Reply-To: <1273105838-4441-1-git-send-email-xiaosuo@gmail.com>
Changli Gao wrote:
> kvmalloc() will try to allocate physically contiguous memory first, and try
> vmalloc to allocate virtually contiguous memory when the former allocation
> fails.
Note that converting users from vmalloc() to kvmalloc() may increase
fragmentation problems for other parts of the kernel, because it will
tend to use up more of the available large blocks. Especially users
who allocate large blocks and often. That's worth a mention
somewhere.
On the other hand, this API could make it easier to convert some kmalloc()
calls to kvmalloc(), reducing fragmentation problems. :-)
Since the caller is indicating they don't mind which happens, then
anti-fragmentation heuristics (such as checking watermarks) could be
added to kvmalloc() at some future time, if needed.
-- Jamie
next prev parent reply other threads:[~2010-05-06 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 0:30 [RFC] mm: generic adaptive large memory allocation APIs Changli Gao
2010-05-06 0:37 ` Changli Gao
2010-05-06 1:25 ` Changli Gao
2010-05-06 3:12 ` Tetsuo Handa
2010-05-06 3:22 ` Changli Gao
2010-05-06 15:35 ` Jamie Lokier [this message]
2010-05-07 4:32 ` Changli Gao
2010-05-07 12:42 ` Tetsuo Handa
2010-05-07 12:52 ` Peter Zijlstra
2010-05-13 4:45 ` KOSAKI Motohiro
2010-05-13 8:43 ` Jiri Slaby
2010-05-13 9:05 ` KOSAKI Motohiro
2010-05-13 9:19 ` Jiri Slaby
2010-05-13 9:40 ` KOSAKI Motohiro
2010-05-13 10:16 ` Jiri Slaby
2010-05-13 10:43 ` KOSAKI Motohiro
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=20100506153546.GC28512@shareable.org \
--to=jamie@shareable.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xiaosuo@gmail.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;
as well as URLs for NNTP newsgroup(s).