From: William Lee Irwin III <wli@holomorphy.com>
To: Adam Litke <agl@us.ibm.com>
Cc: akpm@osdl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
hugh@veritas.com, rohit.seth@intel.com, kenneth.w.chen@intel.com
Subject: Re: [PATCH 4/4] Hugetlb: Copy on Write support
Date: Wed, 9 Nov 2005 16:15:34 -0800 [thread overview]
Message-ID: <20051110001534.GN29402@holomorphy.com> (raw)
In-Reply-To: <1131579596.28383.25.camel@localhost.localdomain>
On Wed, Nov 09, 2005 at 05:39:55PM -0600, Adam Litke wrote:
> Hugetlb: Copy on Write support
> Implement copy-on-write support for hugetlb mappings so MAP_PRIVATE can be
> supported. This helps us to safely use hugetlb pages in many more
> applications. The patch makes the following changes. If needed, I also have
> it broken out according to the following paragraphs.
> 1. Add a pair of functions to set/clear write access on huge ptes. The
> writable check in make_huge_pte is moved out to the caller for use by COW
> later.
> 2. Hugetlb copy-on-write requires special case handling in the following
> situations:
> - copy_hugetlb_page_range() - Copied pages must be write protected so a COW
> fault will be triggered (if necessary) if those pages are written to.
> - find_or_alloc_huge_page() - Only MAP_SHARED pages are added to the page
> cache. MAP_PRIVATE pages still need to be locked however.
> 3. Provide hugetlb_cow() and calls from hugetlb_fault() and hugetlb_no_page()
> which handles the COW fault by making the actual copy.
> 4. Remove the check in hugetlbfs_file_map() so that MAP_PRIVATE mmaps will be
> allowed. Make MAP_HUGETLB exempt from the depricated VM_RESERVED mapping
> check.
Did you do the audit of pte protection bits I asked about? If not, I'll
dredge them up and check to make sure.
-- wli
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Adam Litke <agl@us.ibm.com>
Cc: akpm@osdl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>,
hugh@veritas.com, rohit.seth@intel.com, kenneth.w.chen@intel.com
Subject: Re: [PATCH 4/4] Hugetlb: Copy on Write support
Date: Wed, 9 Nov 2005 16:15:34 -0800 [thread overview]
Message-ID: <20051110001534.GN29402@holomorphy.com> (raw)
In-Reply-To: <1131579596.28383.25.camel@localhost.localdomain>
On Wed, Nov 09, 2005 at 05:39:55PM -0600, Adam Litke wrote:
> Hugetlb: Copy on Write support
> Implement copy-on-write support for hugetlb mappings so MAP_PRIVATE can be
> supported. This helps us to safely use hugetlb pages in many more
> applications. The patch makes the following changes. If needed, I also have
> it broken out according to the following paragraphs.
> 1. Add a pair of functions to set/clear write access on huge ptes. The
> writable check in make_huge_pte is moved out to the caller for use by COW
> later.
> 2. Hugetlb copy-on-write requires special case handling in the following
> situations:
> - copy_hugetlb_page_range() - Copied pages must be write protected so a COW
> fault will be triggered (if necessary) if those pages are written to.
> - find_or_alloc_huge_page() - Only MAP_SHARED pages are added to the page
> cache. MAP_PRIVATE pages still need to be locked however.
> 3. Provide hugetlb_cow() and calls from hugetlb_fault() and hugetlb_no_page()
> which handles the COW fault by making the actual copy.
> 4. Remove the check in hugetlbfs_file_map() so that MAP_PRIVATE mmaps will be
> allowed. Make MAP_HUGETLB exempt from the depricated VM_RESERVED mapping
> check.
Did you do the audit of pte protection bits I asked about? If not, I'll
dredge them up and check to make sure.
-- wli
--
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-10 0:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 23:28 [PATCH 0/4] hugetlb: copy on write Adam Litke
2005-11-09 23:28 ` Adam Litke
2005-11-09 23:36 ` [PATCH 1/4] Hugetlb: Remove duplicate i_size check Adam Litke
2005-11-09 23:36 ` Adam Litke
2005-11-10 0:10 ` William Lee Irwin III
2005-11-10 0:10 ` William Lee Irwin III
2005-11-09 23:37 ` [PATCH 2/4] Hugetlb: Rename find_lock_page to find_or_alloc_huge_page Adam Litke
2005-11-09 23:37 ` Adam Litke
2005-11-10 0:11 ` William Lee Irwin III
2005-11-10 0:11 ` William Lee Irwin III
2005-11-09 23:38 ` [PATCH 3/4] Hugetlb: Reorganize hugetlb_fault to prepare for COW Adam Litke
2005-11-09 23:38 ` Adam Litke
2005-11-10 0:13 ` William Lee Irwin III
2005-11-10 0:13 ` William Lee Irwin III
2005-11-09 23:39 ` [PATCH 4/4] Hugetlb: Copy on Write support Adam Litke
2005-11-09 23:39 ` Adam Litke
2005-11-10 0:15 ` William Lee Irwin III [this message]
2005-11-10 0:15 ` William Lee Irwin III
2005-11-10 0:49 ` David Gibson
2005-11-10 0:49 ` David Gibson
2005-11-10 0:56 ` William Lee Irwin III
2005-11-10 0:56 ` William Lee Irwin III
2005-11-10 1:52 ` Rohit Seth
2005-11-10 1:52 ` Rohit Seth
2005-11-10 3:54 ` David Gibson
2005-11-10 3:54 ` David Gibson
2005-11-10 4:20 ` William Lee Irwin III
2005-11-10 4:20 ` William Lee Irwin III
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=20051110001534.GN29402@holomorphy.com \
--to=wli@holomorphy.com \
--cc=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.