[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F87@exch03.qd.lucent.com>
Date: Sat, 28 Apr 2007 21:58:49 +0800
From: "Shan, Guo Wen (Gavin)" <gshan@...atel-lucent.com>
To: "Robert P. J. Day" <rpjday@...dspring.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: can a kmalloc be both GFP_ATOMIC and GFP_KERNEL at the same time?
#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@...dspring.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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists