From: Thomas Gleixner <tglx@linutronix.de>
To: David Rientjes <rientjes@google.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Make GFP_DMA allocations w/o ZONE_DMA emit a warning instead of failing
Date: Wed, 1 Jun 2011 21:46:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1106012134120.3078@ionos> (raw)
In-Reply-To: <alpine.DEB.2.00.1106011205410.17065@chino.kir.corp.google.com>
On Wed, 1 Jun 2011, David Rientjes wrote:
> On Wed, 1 Jun 2011, Thomas Gleixner wrote:
>
> > > That is NOT an unreasonable request, but it seems that its far too much
> > > to ask of you.
> >
> > Full ack.
> >
> > David,
> >
> > stop that nonsense already. You changed the behaviour and broke stuff
> > which was working fine before for whatever reason. That behaviour was
> > in the kernel for ages and we tolerated the abuse.
> >
>
> Did I nack this patch and not realize it?
No, you did not realize anything.
> Does my patch fix the warning for pxaficp_ir that would still be emitted
> with this patch? If the driver uses GFP_DMA and nobody from the arm side
Your patch does not fix anything. It papers over the problem and
that's the f@&^%%@^#ing wrong approach.
And just to be clear. You CANNOT fix a warning. You can fix the code
which causes the warning, but that's not what your patch is
doing. Your patch HIDES the problem.
> is prepared to remove it yet, then I'd suggest merging my patch until that
> can be determined. Otherwise, you have no guarantees about where the
> memory is actually coming from.
Did you actually try to understand what I wrote?
You decided that it's a BUG just because it should not be allowed. So
you changed the behaviour, which was perfectly fine before.
Now you try to paper over the problem by selecting ZONE_DMA and refuse
to give a grace period of _ONE_ kernel release.
IOW, you are preventing that the abusers of GFP_DMA are fixed
properly.
I can see that you neither have the bandwidth nor the knowledge to
analyse each user of GFP_DMA. And that should tell you something.
If you cannot fix it yourself, then f*(&!@$#ng not break it.
Thanks,
tglx
next prev parent reply other threads:[~2011-06-01 19:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:04 [PATCH] Make GFP_DMA allocations w/o ZONE_DMA emit a warning instead of failing 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 [this message]
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
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.LFD.2.02.1106012134120.3078@ionos \
--to=tglx@linutronix.de \
--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=riel@redhat.com \
--cc=rientjes@google.com \
/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