From: Andrew Morton <akpm@linux-foundation•org>
To: Eric Munson <ebmunson@us•ibm.com>
Cc: linux-mm@kvack•org, libhugetlbfs-devel@lists•sourceforge.net,
linux-kernel@vger•kernel.org, linuxppc-dev@ozlabs•org
Subject: Re: [RFC] [PATCH 0/5 V2] Huge page backed user-space stacks
Date: Wed, 30 Jul 2008 01:41:39 -0700 [thread overview]
Message-ID: <20080730014139.39b3edc5.akpm@linux-foundation.org> (raw)
In-Reply-To: <cover.1216928613.git.ebmunson@us.ibm.com>
On Mon, 28 Jul 2008 12:17:10 -0700 Eric Munson <ebmunson@us•ibm.com> wrote:
> Certain workloads benefit if their data or text segments are backed by
> huge pages. The stack is no exception to this rule but there is no
> mechanism currently that allows the backing of a stack reliably with
> huge pages. Doing this from userspace is excessively messy and has some
> awkward restrictions. Particularly on POWER where 256MB of address space
> gets wasted if the stack is setup there.
>
> This patch stack introduces a personality flag that indicates the kernel
> should setup the stack as a hugetlbfs-backed region. A userspace utility
> may set this flag then exec a process whose stack is to be backed by
> hugetlb pages.
>
> Eric Munson (5):
> Align stack boundaries based on personality
> Add shared and reservation control to hugetlb_file_setup
> Split boundary checking from body of do_munmap
> Build hugetlb backed process stacks
> [PPC] Setup stack memory segment for hugetlb pages
>
> arch/powerpc/mm/hugetlbpage.c | 6 +
> arch/powerpc/mm/slice.c | 11 ++
> fs/exec.c | 209 ++++++++++++++++++++++++++++++++++++++---
> fs/hugetlbfs/inode.c | 52 +++++++----
> include/asm-powerpc/hugetlb.h | 3 +
> include/linux/hugetlb.h | 22 ++++-
> include/linux/mm.h | 1 +
> include/linux/personality.h | 3 +
> ipc/shm.c | 2 +-
> mm/mmap.c | 11 ++-
> 10 files changed, 284 insertions(+), 36 deletions(-)
That all looks surprisingly straightforward.
Might there exist an x86 port which people can play with?
next prev parent reply other threads:[~2008-07-30 8:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 19:17 [RFC] [PATCH 0/5 V2] Huge page backed user-space stacks Eric Munson
2008-07-28 19:17 ` [PATCH 1/5 V2] Align stack boundaries based on personality Eric Munson
2008-07-28 20:09 ` Dave Hansen
2008-07-28 19:17 ` [PATCH 2/5 V2] Add shared and reservation control to hugetlb_file_setup Eric Munson
2008-07-28 19:17 ` [PATCH 3/5] Split boundary checking from body of do_munmap Eric Munson
2008-07-28 19:17 ` [PATCH 4/5 V2] Build hugetlb backed process stacks Eric Munson
2008-07-28 20:37 ` Dave Hansen
2008-07-28 19:17 ` [PATCH 5/5 V2] [PPC] Setup stack memory segment for hugetlb pages Eric Munson
2008-07-28 20:33 ` [RFC] [PATCH 0/5 V2] Huge page backed user-space stacks Dave Hansen
2008-07-28 21:23 ` Eric B Munson
2008-07-30 8:41 ` Andrew Morton [this message]
2008-07-30 15:04 ` Eric B Munson
2008-07-30 15:08 ` Eric B Munson
2008-07-30 8:43 ` Andrew Morton
2008-07-30 17:23 ` Mel Gorman
2008-07-30 17:34 ` Andrew Morton
2008-07-30 19:30 ` Mel Gorman
2008-07-30 19:40 ` Christoph Lameter
2008-07-30 20:07 ` Andrew Morton
2008-07-31 10:31 ` Mel Gorman
2008-08-04 21:10 ` Dave Hansen
2008-08-05 11:11 ` Mel Gorman
2008-08-05 16:12 ` Dave Hansen
2008-08-05 16:28 ` Mel Gorman
2008-08-05 17:53 ` Dave Hansen
2008-08-06 9:02 ` Mel Gorman
2008-08-06 19:50 ` Dave Hansen
2008-08-07 16:06 ` Mel Gorman
2008-08-07 17:29 ` Dave Hansen
2008-08-11 8:04 ` Mel Gorman
2008-07-31 6:04 ` Nick Piggin
2008-07-31 6:14 ` Andrew Morton
2008-07-31 6:26 ` Nick Piggin
2008-07-31 11:27 ` Mel Gorman
2008-07-31 11:51 ` Nick Piggin
2008-07-31 13:50 ` Mel Gorman
2008-07-31 14:32 ` Michael Ellerman
2008-08-06 18:49 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080730014139.39b3edc5.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=ebmunson@us$(echo .)ibm.com \
--cc=libhugetlbfs-devel@lists$(echo .)sourceforge.net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox