From: Eric B Munson <ebmunson@us.ibm.com>
To: Dave Hansen <dave@linux.vnet.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: Mon, 28 Jul 2008 14:23:54 -0700 [thread overview]
Message-ID: <20080728212354.GB8450@us.ibm.com> (raw)
In-Reply-To: <1217277204.23502.36.camel@nimitz>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Mon, 28 Jul 2008, Dave Hansen wrote:
> On Mon, 2008-07-28 at 12:17 -0700, Eric Munson wrote:
> >
> > 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.
>
> I didn't see it mentioned here, but these stacks are fixed-size, right?
> They can't actually grow and are fixed in size at exec() time, right?
>
> -- Dave
The stack VMA is a fixed size but the pages will be faulted in as needed.
--
Eric B Munson
IBM Linux Technology Center
ebmunson@us.ibm.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-28 21:24 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 [this message]
2008-07-30 8:41 ` Andrew Morton
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=20080728212354.GB8450@us.ibm.com \
--to=ebmunson@us.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=libhugetlbfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).