From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Nick Piggin <npiggin@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: percpu allocator vs reclaim
Date: Thu, 05 Mar 2009 01:40:18 +0900 [thread overview]
Message-ID: <49AEAEF2.7040908@kernel.org> (raw)
In-Reply-To: <1236184563.5330.8074.camel@laptop>
Peter Zijlstra wrote:
> Hi Tejun,
>
> Thomas hit the below on recent -tip kernels.
>
> Which basically states that we could deadlock due to reclaim lock
> recursion.
>
> Looking at the code I don't see a quick solution, other than using
> GFP_NOFS, which is a bit of a bother (as I suspect it might easily grow
> __GFP_IO inversion too, if it doesn't already have it).
Ah... maybe percpu allocator should just swallow @gfp. Any better
ideas? :-(
--
tejun
next prev parent reply other threads:[~2009-03-04 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 16:36 percpu allocator vs reclaim Peter Zijlstra
2009-03-04 16:40 ` Tejun Heo [this message]
2009-03-04 16:49 ` Peter Zijlstra
2009-03-05 8:11 ` Tejun Heo
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=49AEAEF2.7040908@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.