Re: [13/18] x86_64: Allow fallback for the stack

> The order-1 allocation failures where GFP_ATOMIC, because SLUB uses !0
> order for everything.

slub is wrong then. Can it be fixed?

> Kernel stack allocation is GFP_KERNEL I presume. 

Of course.

> Also, I use 4k stacks on all my machines.

You don't have any x86-64 machines?

-Andi
-
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: [13/18] x86_64: Allow fallback for the stack
    • From: Christoph Lameter <[email protected]>
  • Re: [13/18] x86_64: Allow fallback for the stack
    • From: Peter Zijlstra <[email protected]>

• References:
  • [00/18] Virtual Compound Page Support V2
    • From: Christoph Lameter <[email protected]>
  • Re: [13/18] x86_64: Allow fallback for the stack
    • From: Andi Kleen <[email protected]>
  • Re: [13/18] x86_64: Allow fallback for the stack
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: [PATCH 1/3] signal(i386): alternative signal stack wraparound occurs
• Next by Date: [PATCH] remove throttle_vm_writeout()
• Previous by thread: Re: [13/18] x86_64: Allow fallback for the stack
• Next by thread: Re: [13/18] x86_64: Allow fallback for the stack
• 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]