Re: [2.6 patch] i386: always use 4k stacks

From: Andi Kleen (ak_at_suse.de)
Date: 11/16/05

  • Next message: Linus Torvalds: "Re: [PATCH 12/18] shared mount handling: bind and rbind" 
    To: Arjan van de Ven <arjan@infradead.org>
Date:	Wed, 16 Nov 2005 17:10:04 +0100

    On Wednesday 16 November 2005 16:38, Arjan van de Ven wrote:
    > On Wed, 2005-11-16 at 16:30 +0100, Oliver Neukum wrote:
    > > Am Mittwoch, 16. November 2005 15:42 schrieb jmerkey:
    > > > Map a blank ro page beneath the address range when stack memory is
    > > > mapped is trap on page faults to the page when folks go off the end of
    > > > th e stack.
    > > >
    > > > Easy to find.
    > >
    > > Provided you can easily trigger it. I don't see how that is a given.
    >
    > the same is true for a unified 8k stack or for the 4k/4k split though.
    > Ok sure there's a 1.5Kb difference on the one side.. (but a 2Kb gain on
    > the other side)

    I was always in favour of 8K process stacks + irq stacks. Works great on x86-64.

    -Andi
    -
    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/

  • Next message: Linus Torvalds: "Re: [PATCH 12/18] shared mount handling: bind and rbind"

    Relevant Pages