From: Adam Litke <agl@us.ibm.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
hugh@veritas.com, rohit.seth@intel.com, "Chen,
Kenneth W" <kenneth.w.chen@intel.com>,
akpm@osdl.org
Subject: Re: [RFC 2/2] Hugetlb COW
Date: Mon, 07 Nov 2005 15:47:55 -0600 [thread overview]
Message-ID: <1131400076.25133.110.camel@localhost.localdomain> (raw)
In-Reply-To: <1131399533.25133.104.camel@localhost.localdomain>
On Mon, 2005-11-07 at 15:38 -0600, Adam Litke wrote:
> [RFC] COW for hugepages
> (Patch originally from David Gibson <dwg@au1.ibm.com>)
>
> This patch implements copy-on-write for hugepages, hence allowing
> MAP_PRIVATE mappings of hugetlbfs.
>
> This is chiefly useful for cases where we want to use hugepages
> "automatically" - that is to map hugepages without the knowledge of
> the code in the final application (either via kernel hooks, or with
> LD_PRELOAD). We can use various heuristics to determine when
> hugepages might be a good idea, but changing the semantics of
> anonymous memory from MAP_PRIVATE to MAP_SHARED without the app's
> knowledge is clearly wrong.
I forgot to mention in the original post that this patch is currently
broken on ppc64 due to a problem with update_mmu_cache(). The proper
fix is understood but backed up behind the powerpc merge activity.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Adam Litke <agl@us.ibm.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
hugh@veritas.com, rohit.seth@intel.com, "Chen,
Kenneth W" <kenneth.w.chen@intel.com>,
akpm@osdl.org
Subject: Re: [RFC 2/2] Hugetlb COW
Date: Mon, 07 Nov 2005 15:47:55 -0600 [thread overview]
Message-ID: <1131400076.25133.110.camel@localhost.localdomain> (raw)
In-Reply-To: <1131399533.25133.104.camel@localhost.localdomain>
On Mon, 2005-11-07 at 15:38 -0600, Adam Litke wrote:
> [RFC] COW for hugepages
> (Patch originally from David Gibson <dwg@au1.ibm.com>)
>
> This patch implements copy-on-write for hugepages, hence allowing
> MAP_PRIVATE mappings of hugetlbfs.
>
> This is chiefly useful for cases where we want to use hugepages
> "automatically" - that is to map hugepages without the knowledge of
> the code in the final application (either via kernel hooks, or with
> LD_PRELOAD). We can use various heuristics to determine when
> hugepages might be a good idea, but changing the semantics of
> anonymous memory from MAP_PRIVATE to MAP_SHARED without the app's
> knowledge is clearly wrong.
I forgot to mention in the original post that this patch is currently
broken on ppc64 due to a problem with update_mmu_cache(). The proper
fix is understood but backed up behind the powerpc merge activity.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
--
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>
next prev parent reply other threads:[~2005-11-07 21:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 21:10 [RFC 0/2] Copy on write for hugetlbfs Adam Litke
2005-11-07 21:10 ` Adam Litke
2005-11-07 21:38 ` [RFC 1/2] Hugetlb fault fixes and reorg Adam Litke
2005-11-07 21:38 ` Adam Litke
2005-11-07 23:30 ` William Lee Irwin III
2005-11-07 23:30 ` William Lee Irwin III
2005-11-08 1:21 ` David Gibson
2005-11-08 1:21 ` David Gibson
2005-11-07 21:38 ` [RFC 2/2] Hugetlb COW Adam Litke
2005-11-07 21:38 ` Adam Litke
2005-11-07 21:47 ` Adam Litke [this message]
2005-11-07 21:47 ` Adam Litke
2005-11-08 3:44 ` David Gibson
2005-11-08 3:44 ` David Gibson
2005-11-08 4:17 ` David Gibson
2005-11-08 4:17 ` David Gibson
2005-11-07 23:35 ` William Lee Irwin III
2005-11-07 23:35 ` William Lee Irwin III
2005-11-08 2:53 ` David Gibson
2005-11-08 2:53 ` David Gibson
2005-11-08 3:46 ` David Gibson
2005-11-08 3:46 ` David Gibson
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=1131400076.25133.110.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--cc=hugh@veritas.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rohit.seth@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.