Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020

On Thu, 10 May 2007, Mel Gorman wrote:

> I see the gfpmask was 0x84020. That doesn't look like __GFP_WAIT was set,
> right? Does that mean that SLUB is trying to allocate pages atomically? If so,
> it would explain why this situation could still occur even though high-order
> allocations that could sleep would succeed.

SLUB is following the gfp mask of the caller like all well behaved slab 
allocators do. If the caller does not set __GFP_WAIT then the page 
allocator also cannot wait.
-
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/

---

• Follow-Ups:
  • Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
    • From: [email protected] (Mel Gorman)

• References:
  • Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
    • From: Andrew Morton <[email protected]>
  • Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
    • From: Christoph Lameter <[email protected]>
  • Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
    • From: [email protected] (Mel Gorman)

• Prev by Date: Re: [PATCH] Make modpost section warnings clearer
• Next by Date: Re: [1/2] [NET] link_watch: Move link watch list into net_device
• Previous by thread: Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
• Next by thread: Re: [Bug 8464] New: autoreconf: page allocation failure. order:2, mode:0x84020
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]