From: Pavel Machek <pavel@ucw.cz>
To: David Rientjes <rientjes@google.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
stable@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Frans Pop <elendil@planet.nl>,
Jiri Kosina <jkosina@suse.cz>,
Sven Geggus <lists@fuchsschwanzdomain.de>,
Karol Lewandowski <karol.k.lewandowski@gmail.com>,
Tobias Oetiker <tobi@oetiker.ch>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Stephan von Krawczynski <skraw@ithnet.com>,
kernel-testers@vger.kernel.org
Subject: Re: [PATCH 2/3] page allocator: Do not allow interrupts to use ALLOC_HARDER
Date: Wed, 4 Nov 2009 10:01:40 +0100 [thread overview]
Message-ID: <20091104090140.GA14694@elf.ucw.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.0911031739380.1187@chino.kir.corp.google.com>
> I hope we can move this to another thread if people would like to remove
> this exemption completely instead of talking about this trivial fix, which
> I doubt there's any objection to.
I'm arguing that this "trivial fix" is wrong, and that you should just
remove those two lines.
If going into reserves from interrupts hurts, doing that from task
context will hurt, too. "realtime" task should not be normally allowed
to "hurt" the system like that.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-04 9:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:40 [PATCH 0/3] Reduce GFP_ATOMIC allocation failures, partial fix V3 Mel Gorman
2009-10-27 13:40 ` [PATCH 1/3] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed Mel Gorman
2009-10-27 13:40 ` [PATCH 2/3] page allocator: Do not allow interrupts to use ALLOC_HARDER Mel Gorman
[not found] ` <1256650833-15516-3-git-send-email-mel-wPRd99KPJ+uzQB+pC5nmwQ@public.gmane.org>
2009-10-27 20:09 ` Andrew Morton
2009-10-27 21:12 ` David Rientjes
2009-10-31 18:40 ` Pavel Machek
2009-10-31 19:51 ` David Rientjes
2009-10-31 20:11 ` Pavel Machek
2009-10-31 21:19 ` David Rientjes
2009-10-31 22:29 ` Pavel Machek
2009-10-31 22:55 ` Rik van Riel
2009-11-01 7:35 ` Pavel Machek
2009-11-01 12:37 ` KOSAKI Motohiro
2009-11-01 14:44 ` Rik van Riel
2009-11-01 19:32 ` Pavel Machek
2009-11-02 16:38 ` Christoph Lameter
2009-10-31 23:59 ` Rik van Riel
2009-11-02 16:42 ` Christoph Lameter
2009-11-02 20:53 ` David Rientjes
2009-11-03 17:10 ` Christoph Lameter
2009-11-04 1:46 ` David Rientjes
2009-11-04 9:01 ` Pavel Machek [this message]
2009-11-09 10:11 ` Mel Gorman
2009-10-28 10:24 ` Mel Gorman
2009-10-27 13:40 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit Mel Gorman
2009-10-27 18:18 ` Rik van Riel
2009-10-27 20:19 ` Andrew Morton
2009-10-28 3:54 ` KOSAKI Motohiro
2009-10-28 10:29 ` Mel Gorman
2009-10-28 19:47 ` Andrew Morton
2009-11-02 16:05 ` Mel Gorman
2009-11-02 17:32 ` Frans Pop
2009-11-02 17:38 ` Mel Gorman
2009-11-02 20:36 ` Mel Gorman
2009-11-03 22:01 ` Frans Pop
2009-11-03 22:08 ` Mel Gorman
2009-11-04 0:01 ` Frans Pop
2009-11-04 1:18 ` Mel Gorman
2009-11-04 2:05 ` Frans Pop
2009-11-04 2:08 ` Frans Pop
2009-11-04 15:48 ` Mel Gorman
2009-11-04 20:57 ` Frans Pop
2009-11-05 16:48 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit (data on latencies available) Mel Gorman
2009-11-12 11:36 ` Frans Pop
2009-11-04 2:08 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit Mel Gorman
2009-10-28 13:02 ` [PATCH 0/3] Reduce GFP_ATOMIC allocation failures, partial fix V3 Karol Lewandowski
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=20091104090140.GA14694@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=jkosina@suse.cz \
--cc=karol.k.lewandowski@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lists@fuchsschwanzdomain.de \
--cc=mel@csn.ul.ie \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=skraw@ithnet.com \
--cc=stable@kernel.org \
--cc=tobi@oetiker.ch \
/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