From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Nick Piggin <npiggin@suse.de>, Jiri Kosina <jkosina@suse.cz>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: irq lock inversion
Date: Sat, 07 Nov 2009 17:13:32 +0100 [thread overview]
Message-ID: <1257610412.4108.3.camel@laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.0911061159450.5187@V090114053VZO-1>
On Fri, 2009-11-06 at 12:03 -0500, Christoph Lameter wrote:
> Atomic allocs are allowed to fail.
All allocs (except __GFP_NOFAIL, but those are a deadlock waiting to
happen) are allowed to fail, !__GFP_WAIT allocs simply fail more easily.
The fact that __GFP_WAIT && order <= PAGE_ALLOC_COSTLY_ORDER allocations
currently don't fail but keep hammering the allocator could be
considered a bug (the recent OOM threads in fact suggest this is a
serious issue for some people).
next prev parent reply other threads:[~2009-11-07 16:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86802c440911041008q4969b9bdk15b4598c40bb84bd@mail.gmail.com>
[not found] ` <4AF25FC7.4000502@kernel.org>
[not found] ` <20091105082102.GA2870@elte.hu>
[not found] ` <4AF28D7A.6020209@kernel.org>
2009-11-05 14:31 ` irq lock inversion Jiri Kosina
2009-11-06 5:53 ` Tejun Heo
2009-11-06 7:17 ` Ingo Molnar
2009-11-06 7:45 ` Tejun Heo
2009-11-06 7:58 ` Ingo Molnar
2009-11-06 8:24 ` Tejun Heo
2009-11-06 8:40 ` Ingo Molnar
2009-11-06 8:52 ` Tejun Heo
2009-11-06 16:08 ` Christoph Lameter
2009-11-06 16:38 ` Tejun Heo
2009-11-06 17:03 ` Christoph Lameter
2009-11-07 16:13 ` Peter Zijlstra [this message]
2009-11-09 5:46 ` [PATCH percpu#for-linus] percpu: fix possible deadlock via " Tejun Heo
2009-11-06 9:59 ` Jens Axboe
2009-11-08 9:38 ` Ingo Molnar
2009-11-09 15:34 ` Jens Axboe
2009-11-09 15:45 ` Ingo Molnar
2009-11-09 15:49 ` Jens Axboe
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=1257610412.4108.3.camel@laptop \
--to=peterz@infradead.org \
--cc=cl@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=yhlu.kernel@gmail.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