From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Marc Singer <elf@buici.com>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: DMA memory, split_page, BUG_ON(PageCompound()), sound
Date: Tue, 11 Jul 2006 03:34:11 +1000 [thread overview]
Message-ID: <44B28F93.9020304@yahoo.com.au> (raw)
In-Reply-To: <20060710162600.GB18728@flint.arm.linux.org.uk>
Russell King wrote:
> 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?
I believe that should do the trick, yes (AFAIK, nobody yet is
explicitly relying on a compound page from the dma allocator).
Marc can hopefully confim the fix.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-07-10 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 0:07 DMA memory, split_page, BUG_ON(PageCompound()), sound Marc Singer
2006-07-09 3:26 ` Nick Piggin
2006-07-10 2:51 ` Marc Singer
2006-07-10 6:59 ` Nick Piggin
2006-07-10 16:26 ` Russell King
2006-07-10 17:34 ` Nick Piggin [this message]
2006-07-10 22:27 ` Marc Singer
2006-07-11 2:51 ` Marc Singer
2006-07-12 10:32 ` Russell King
2006-07-13 13:30 ` Takashi Iwai
2006-07-13 13:38 ` Nick Piggin
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=44B28F93.9020304@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=elf@buici.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.