From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
tglx@linutronix.de, rientjes@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mel@csn.ul.ie,
kamezawa.hiroyu@jp.fujitsu.com, riel@redhat.com, pavel@ucw.cz
Subject: Re: [PATCH] Make GFP_DMA allocations w/o ZONE_DMA emit a warning instead of failing
Date: Fri, 10 Jun 2011 10:12:33 +0100 [thread overview]
Message-ID: <20110610091233.GJ24424@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTimC8K2_H7ZEu2XYoWdA09-3XxpV7Q@mail.gmail.com>
On Fri, Jun 10, 2011 at 12:11:42PM +0400, Dmitry Eremin-Solenikov wrote:
> On 6/10/11, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Fri, 10 Jun 2011 16:38:06 +0900 KOSAKI Motohiro
> > <kosaki.motohiro@jp.fujitsu.com> wrote:
> >
> >> Subject: [PATCH] Revert "mm: fail GFP_DMA allocations when ZONE_DMA is not
> >> configured"
> >
> > Confused. We reverted this over a week ago.
>
> Should one submit a patch adding a warning to GFP_DMA allocations
> w/o ZONE_DMA, or the idea of the original patch is wrong?
Linus was far from impressed by the original commit, saying:
| Using GFP_DMA is reasonable in a driver - on platforms where that
| matters, it should allocate from the DMA zone, on platforms where it
| doesn't matter it should be a no-op.
So no, not even a warning.
What is a useful exercise though is to remove GFP_DMA from those
allocations which should never have had GFP_DMA added - such as those
used for data structures which have nothing to do with DMA at all.
Also dma_alloc_coherent() should not be given GFP_DMA in any case.
--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-10 9:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:04 Dmitry Eremin-Solenikov
2011-06-01 12:38 ` KOSAKI Motohiro
2011-06-01 15:07 ` Dmitry Eremin-Solenikov
2011-06-01 17:23 ` David Rientjes
2011-06-01 18:19 ` Russell King - ARM Linux
2011-06-01 18:55 ` Thomas Gleixner
2011-06-01 19:09 ` David Rientjes
2011-06-01 19:46 ` Thomas Gleixner
2011-06-10 7:38 ` KOSAKI Motohiro
2011-06-10 7:43 ` Andrew Morton
2011-06-10 7:52 ` KOSAKI Motohiro
2011-06-10 8:11 ` Dmitry Eremin-Solenikov
2011-06-10 9:12 ` Russell King - ARM Linux [this message]
2011-06-10 18:54 ` David Rientjes
2011-06-10 18:58 ` Russell King - ARM Linux
2011-06-10 22:01 ` David Rientjes
2011-06-10 22:07 ` Russell King - ARM Linux
2011-06-10 22:16 ` David Rientjes
2011-06-10 22:20 ` Russell King - ARM Linux
2011-06-10 22:30 ` David Rientjes
2011-06-11 9:45 ` Catalin Marinas
2011-06-11 17:18 ` Robert Hancock
2011-06-12 13:48 ` Russell King - ARM Linux
2011-06-01 18:30 ` Dmitry Eremin-Solenikov
2011-06-01 18:42 ` David Rientjes
2011-06-02 21:46 ` Pavel Machek
2011-06-12 11:07 ` Rafael J. Wysocki
2011-06-12 11:33 ` Cyril Hrubis
2011-06-12 11:39 ` Rafael J. Wysocki
2011-06-10 22:24 ` Linus Torvalds
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=20110610091233.GJ24424@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=pavel@ucw.cz \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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