From: Christoph Lameter <clameter@sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
"Shan, Guo Wen (Gavin)" <gshan@alcatel-lucent.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: can a kmalloc be both GFP_ATOMIC and GFP_KERNEL at the same time?
Date: Sun, 29 Apr 2007 22:58:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704292257080.2910@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070428172939.35689110@the-village.bc.nu>
On Sat, 28 Apr 2007, Alan Cox wrote:
> > > drivers/scsi/aic7xxx_old.c: aic_dev = kmalloc(sizeof(struct aic_dev_data), GFP_ATOMIC | GFP_KERNEL);
> > > drivers/message/i2o/device.c: resblk = kmalloc(buflen + 8, GFP_KERNEL | GFP_ATOMIC);
> > >
> > > clarification?
> >
> > oh, i'm *aware* of the definitions of those flags, but every single
> > source i've ever read has *strongly* suggested that you don't use
>
> I don't believe either of those is doing what the author intended 8).
Well sortof. First of all kmalloc may not even allocate a page to
satisfy the request. If it does then we do essentially GFP_KERNEL |
__GFP_HIGH meaning a allocation where we can sleep etc but are allowed to
dip into the reserves.
next prev parent reply other threads:[~2007-04-30 5:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 13:58 Shan, Guo Wen (Gavin)
2007-04-28 14:11 ` Robert P. J. Day
2007-04-28 15:03 ` Arjan van de Ven
2007-04-28 15:20 ` WANG Cong
2007-04-28 16:29 ` Alan Cox
2007-04-30 5:58 ` Christoph Lameter [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 13:40 Robert P. J. Day
2007-04-30 7:13 ` Andrew Morton
2007-04-30 8:46 ` Robert P. J. Day
2007-04-30 8:56 ` Jan Engelhardt
2007-04-30 9:52 ` Robert P. J. Day
2007-04-30 12:00 ` Satyam Sharma
2007-04-30 17:02 ` Andrew Morton
2007-04-30 17:21 ` Alan Cox
2007-04-30 19:04 ` Satyam Sharma
2007-04-30 22:42 ` Stefan Richter
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=Pine.LNX.4.64.0704292257080.2910@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gshan@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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
all inboxes | Powered by JetHome®