mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shan, Guo Wen (Gavin)" <gshan@alcatel-lucent.com>
To: "Robert P. J. Day" <rpjday@mindspring.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: Sat, 28 Apr 2007 21:58:49 +0800	[thread overview]
Message-ID: <2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F87@exch03.qd.lucent.com> (raw)


#define GFP_ATOMIC      (__GFP_HIGH)
#define GFP_NOIO        (__GFP_WAIT)
#define GFP_NOFS        (__GFP_WAIT | __GFP_IO)
#define GFP_KERNEL      (__GFP_WAIT | __GFP_IO | __GFP_FS)

-----Original Message-----
From: Robert P. J. Day [mailto:rpjday@mindspring.com]
Sent: Saturday, April 28, 2007 9:41 PM
To: Linux Kernel Mailing List
Subject: can a kmalloc be both GFP_ATOMIC and GFP_KERNEL at the same
time?



  i'd always assumed that the type flags of GFP_ATOMIC and GFP_KERNEL
were mutually exclusive when it came to calling kmalloc(), at least
based on everything i'd read.  so i'm not sure how to interpret the
following:

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?

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2007-04-28 13:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 13:58 Shan, Guo Wen (Gavin) [this message]
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
  -- 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=2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F87@exch03.qd.lucent.com \
    --to=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®