Marcelo Tosatti wrote:
On Tue, Sep 20, 2005 at 03:37:53PM -0600, Christopher Friesen wrote:
oom-killer: gfp_mask=0xd0
So this must be a DMA allocation (see gfp_mask). Stick a "dump_stack()"
to find out who is the allocator.
Checking in gfp.h, I see:
#define __GFP_DMA 0x01
#define __GFP_HIGHMEM 0x02
#define __GFP_WAIT 0x10 /* Can wait and reschedule? */
#define __GFP_HIGH 0x20 /* Should access emergency pools? */
#define __GFP_IO 0x40 /* Can start physical IO? */
#define __GFP_FS 0x80 /* Can call down to low-level FS? */
#define GFP_KERNEL (__GFP_WAIT | __GFP_IO | __GFP_FS)
Thus, it looks like it's not a dma allocation. By my reading, it
appears to be a standard GFP_KERNEL.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |