linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	tglx@linutronix.de, 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 15:30:35 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1106101526390.24646@chino.kir.corp.google.com> (raw)
In-Reply-To: <20110610222020.GP24424@n2100.arm.linux.org.uk>

On Fri, 10 Jun 2011, Russell King - ARM Linux wrote:

> So those platforms which don't have a DMA zone, don't have any problems
> with DMA, yet want to use the very same driver which does have a problem
> on ISA hardware have to also put up with a useless notification that
> their kernel might be broken?
> 
> Are you offering to participate on other architectures mailing lists to
> answer all the resulting queries?
> 

It all depends on the wording of the "warning", it should make it clear 
that this is not always an error condition and only affects certain types 
of hardware which the user may or may not have.  If you have any 
suggestions on how to alter "task (pid): attempted to allocate DMA memory 
without DMA support -- enable CONFIG_ZONE_DMA if needed" to make that more 
clear, be my guest.  The alternative is that the ISA hardware cannot 
handle the memory returned fails unexpectedly and randomly without any 
clear indication of what the issue is.  I think what would be worse is 
time lost for someone to realize CONFIG_ZONE_DMA isn't enabled, and that 
could be significant (and probably generate many bug reports on its own) 
since it isn't immediately obvious without doing some debugging.

--
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>

  reply	other threads:[~2011-06-10 22:31 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
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 [this message]
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=alpine.DEB.2.00.1106101526390.24646@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --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=linux@arm.linux.org.uk \
    --cc=mel@csn.ul.ie \
    --cc=pavel@ucw.cz \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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