Re: Propagating GFP_NOFS inside __vmalloc()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 17 Nov 2010 01:18:27 -0600 Andreas Dilger <andreas.dilger@xxxxxxxxxx> wrote:

> On 2010-11-16, at 16:11, Andrew Morton wrote:
> > On Mon, 15 Nov 2010 13:28:54 -0800 (PST)
> > David Rientjes <rientjes@xxxxxxxxxx> 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@xxxxxxxxxx  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@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]