linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: ebmunson@us.ibm.com, linux-mm@kvack.org,
	nacc <nacc@linux.vnet.ibm.com>, andyw <andyw@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH 1/2] Add shared and reserve control to hugetlb_file_setup
Date: Mon, 5 May 2008 11:58:27 +0100	[thread overview]
Message-ID: <20080505105826.GA11027@csn.ul.ie> (raw)
In-Reply-To: <1209744977.7763.29.camel@nimitz.home.sr71.net>

On (02/05/08 09:16), Dave Hansen didst pronounce:
> 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()?
> 

hugetlb_file_setup() uses an internal mount to create files just for
SHM. However, it does the work necessary for MAP_SHARED mappings,
particularly reserve pages. The account is currently all fouled up to
deal with a private mapping that has reserves. Teaching
hugetlb_file_setup() to deal with private and shared mappings does
appear the most straight-forward route.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-05-05 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  1:51 Eric B Munson
2008-05-02 16:16 ` Dave Hansen
2008-05-02 21:55   ` Eric B Munson
2008-05-05 10:58   ` Mel Gorman [this message]
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=20080505105826.GA11027@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=andyw@linux.vnet.ibm.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=ebmunson@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --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