public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Eric B Munson <ebmunson@us.ibm.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, nacc <nacc@linux.vnet.ibm.com>,
	mel@csn.ul.ie, andyw <andyw@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH 1/2] Add shared and reserve control to hugetlb_file_setup
Date: Fri, 02 May 2008 14:55:01 -0700	[thread overview]
Message-ID: <1209765301.8581.18.camel@grover.beaverton.ibm.com> (raw)
In-Reply-To: <1209744977.7763.29.camel@nimitz.home.sr71.net>

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

On Fri, 2008-05-02 at 09:16 -0700, Dave Hansen wrote:
> On Thu, 2008-05-01 at 18:51 -0700, Eric B Munson wrote:
> > In order to back stacks with huge pages, we will want to make hugetlbfs
> > files to back them; these will be used to back private mappings.
> > Currently hugetlb_file_setup creates files to back shared memory segments.
> > Modify this to create both private and shared files,
> 
> Hugetlbfs can currently have private mappings, right?  Why not just use
> the existing ones instead of creating a new variety with
> hugetlb_file_setup()?
> 
> -- Dave
> 

Currently the only way to create a private mapping of a huge page is to
have the file system mounted.  This change allows a huge page private
mapping without mounting the filesystem.

Eric

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

  reply	other threads:[~2008-05-02 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  1:51 [RFC][PATCH 1/2] Add shared and reserve control to hugetlb_file_setup Eric B Munson
2008-05-02 16:16 ` Dave Hansen
2008-05-02 21:55   ` Eric B Munson [this message]
2008-05-05 10:58   ` Mel Gorman
2008-05-06 17:23     ` Dave Hansen

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=1209765301.8581.18.camel@grover.beaverton.ibm.com \
    --to=ebmunson@us.ibm.com \
    --cc=andyw@linux.vnet.ibm.com \
    --cc=dave@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