linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric B Munson <ebmunson@us.ibm.com>
To: linux-mm@kvack.org
Cc: nacc <nacc@linux.vnet.ibm.com>,
	mel@csn.ul.ie, andyw <andyw@linux.vnet.ibm.com>
Subject: [RFC][PATCH 0/2] Huge page backed user-space stacks
Date: Thu, 01 May 2008 18:51:16 -0700	[thread overview]
Message-ID: <1209693076.8483.21.camel@grover.beaverton.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 450 bytes --]

It is beneficial for certain user space processes to use huge pages for
their process stacks rather than small pages.

Presently there is no way for a process to do this.  This patch set
introduces a method for putting user space process stacks on huge pages.
It adds a personality flag that requests huge page backed stacks.  A
user space utility will be required to set the personality flag before
calling exec with for the target process.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2008-05-02  1:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1209693076.8483.21.camel@grover.beaverton.ibm.com \
    --to=ebmunson@us.ibm.com \
    --cc=andyw@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=nacc@linux.vnet.ibm.com \
    /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