On Mon, Jul 10, 2006 at 04:59:48PM +1000, Nick Piggin wrote:
> I guess you could do it a number of ways. Maybe having GFP_USERMAP
> set __GFP_USERMAP|__GFP_COMP, and the arm dma memory allocator can
> strip the __GFP_COMP.
>
> If you get an explicit __GFP_COMP passed down, the allocator doesn't
> know whether that was because they want a user mappable area, or
> really want a compound page (in which case, stripping __GFP_COMP is
> the wrong thing to do).
So I'll mask off __GFP_COMP for the time being in the ARM dma allocator
with a note to this effect?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- DMA memory, split_page, BUG_ON(PageCompound()), sound
- Re: DMA memory, split_page, BUG_ON(PageCompound()), sound
- Re: DMA memory, split_page, BUG_ON(PageCompound()), sound
- Re: DMA memory, split_page, BUG_ON(PageCompound()), sound
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]