From: Paulo Marques <pmarques@grupopie.com>
To: Paul Drynoff <pauldrynoff@gmail.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
akpm@osdl.org, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmalloc man page before 2.6.17
Date: Fri, 26 May 2006 14:23:26 +0100 [thread overview]
Message-ID: <4477014E.6030104@grupopie.com> (raw)
In-Reply-To: <36e6b2150605260344l1ba91d56we2d224d49bde4d8e@mail.gmail.com>
Paul Drynoff wrote:
> [...]
> + * %GFP_USER - Allocate memory on behalf of user. May sleep.
> + *
> + * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
> + *
> + * %GFP_ATOMIC - Allocation will not sleep. Use inside interrupt
> handlers.
I find this comment to be a little misleading. GFP_ATOMIC should be used
on _any_ code that can not sleep, including sections protected by a
spinlock and sections that run with IRQ's disabled, no?
--
Paulo Marques - www.grupopie.com
Pointy-Haired Boss: I don't see anything that could stand in our way.
Dilbert: Sanity? Reality? The laws of physics?
next prev parent reply other threads:[~2006-05-26 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 7:07 [PATCH] kmalloc man page before 2.6.17 Paul Drynoff
2006-05-26 7:17 ` Pekka Enberg
2006-05-26 7:58 ` Paul Drynoff
2006-05-26 8:03 ` Pekka J Enberg
2006-05-26 8:20 ` Paul Drynoff
2006-05-26 9:42 ` Andrey Panin
2006-05-26 9:48 ` Jesper Juhl
2006-05-26 10:44 ` Paul Drynoff
2006-05-26 13:23 ` Paulo Marques [this message]
2006-05-26 14:17 ` Christoph Lameter
2006-05-26 14:55 ` Paul Drynoff
2006-05-26 15:03 ` Christoph Lameter
2006-05-26 19:55 ` Luca
2006-05-27 10:28 ` Martin Waitz
2006-05-26 10:47 ` Paul Drynoff
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=4477014E.6030104@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pauldrynoff@gmail.com \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@osdl.org \
/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.