From: Peter Zijlstra <peterz@infradead.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 0/2][RFC] VFCIPI v3
Date: Tue, 31 Jul 2007 18:22:20 +0200 [thread overview]
Message-ID: <1185898941.12034.22.camel@twins> (raw)
In-Reply-To: <46AF2752.BA47.005A.0@novell.com>
On Tue, 2007-07-31 at 12:14 -0400, Gregory Haskins wrote:
> Out of curiosity and for my own edification: What *is* GFP_ATOMIC meant for?
It is meant as you used it, _except_ for !PREEMPT_RT.
With PREEMPT_RT all allocators are fully preemptable, that is both the
slab as well as the underlying page allocator.
Allocation from atomic context is a BUG() with -rt.
next prev parent reply other threads:[~2007-07-31 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 13:24 [PATCH 0/2][RFC] VFCIPI v3 Gregory Haskins
2007-07-31 13:24 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
2007-07-31 13:24 ` [PATCH 2/2] RT: Add priority inheritance to the VFCIPI facility Gregory Haskins
2007-07-31 14:25 ` [PATCH 0/2][RFC] VFCIPI v3 Peter Zijlstra
2007-07-31 15:33 ` Gregory Haskins
2007-07-31 15:40 ` Peter Zijlstra
2007-07-31 16:14 ` Gregory Haskins
2007-07-31 16:22 ` Peter Zijlstra [this message]
2007-07-31 16:26 ` Gregory Haskins
2007-07-31 16:14 ` Gregory Haskins
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=1185898941.12034.22.camel@twins \
--to=peterz@infradead.org \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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