From: Andrew Morton <akpm@linux-foundation.org>
To: Andreas Dilger <andreas.dilger@oracle.com>
Cc: David Rientjes <rientjes@google.com>,
"Ricardo M. Correia" <ricardo.correia@oracle.com>,
linux-mm@kvack.org, Brian Behlendorf <behlendorf1@llnl.gov>
Subject: Re: Propagating GFP_NOFS inside __vmalloc()
Date: Tue, 16 Nov 2010 23:24:27 -0800 [thread overview]
Message-ID: <20101116232427.c614d12e.akpm@linux-foundation.org> (raw)
In-Reply-To: <ED9181FA-6B0E-4A7B-AA2D-7B976A876557@oracle.com>
On Wed, 17 Nov 2010 01:18:27 -0600 Andreas Dilger <andreas.dilger@oracle.com> wrote:
> On 2010-11-16, at 16:11, Andrew Morton wrote:
> > On Mon, 15 Nov 2010 13:28:54 -0800 (PST)
> > David Rientjes <rientjes@google.com> wrote:
> >
> >> - avoid doing anything other than GFP_KERNEL allocations for __vmalloc():
> >> the only current users are gfs2, ntfs, and ceph (the page allocator
> >> __vmalloc() can be discounted since it's done at boot and GFP_ATOMIC
> >> here has almost no chance of failing since the size is determined based
> >> on what is available).
> >
> > ^^ this
> >
> > Using vmalloc anywhere is lame.
>
> I agree. What we really want is 1MB kmalloc() to work... :-/
meh. Thinking that you require 1MB of virtually contiguous memory in
kernel code is lame.
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-17 7:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 20:42 Propagating GFP_NOFS inside __vmalloc() Ricardo M. Correia
2010-11-10 21:35 ` Ricardo M. Correia
2010-11-10 22:10 ` Dave Chinner
2010-11-11 20:06 ` Andrew Morton
2010-11-11 22:02 ` Ricardo M. Correia
2010-11-11 22:25 ` Andrew Morton
2010-11-11 22:45 ` Ricardo M. Correia
2010-11-11 23:19 ` Ricardo M. Correia
2010-11-11 23:27 ` Andrew Morton
2010-11-11 23:29 ` Ricardo M. Correia
2010-11-15 17:01 ` Ricardo M. Correia
2010-11-15 21:28 ` David Rientjes
2010-11-15 22:19 ` Ricardo M. Correia
2010-11-15 22:50 ` David Rientjes
2010-11-15 23:30 ` Ricardo M. Correia
2010-11-15 23:55 ` David Rientjes
2010-11-16 22:11 ` Andrew Morton
2010-11-17 7:18 ` Andreas Dilger
2010-11-17 7:24 ` Andrew Morton [this message]
2010-11-17 7:37 ` David Rientjes
2010-11-17 9:04 ` Christoph Hellwig
2010-11-17 21:24 ` David Rientjes
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=20101116232427.c614d12e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreas.dilger@oracle.com \
--cc=behlendorf1@llnl.gov \
--cc=linux-mm@kvack.org \
--cc=ricardo.correia@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).