All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Hugh Dickins <hugh@veritas.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [patch 5/6] mm: remap ZERO_PAGE mappings
Date: Tue, 26 Jul 2005 18:20:08 +1000	[thread overview]
Message-ID: <42E5F238.4020302@yahoo.com.au> (raw)
In-Reply-To: <42E5F21B.8090900@yahoo.com.au>

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

5/6


[-- Attachment #2: mm-remap-ZERO_PAGE-mappings.patch --]
[-- Type: text/plain, Size: 1067 bytes --]

Remap ZERO_PAGE ptes when remapping memory. This is currently just an
optimisation for MIPS, which is the only architecture with multiple
zero pages - it now retains the mapping it needs for good cache performance,
and as well do_wp_page is now able to always correctly detect and
optimise zero page COW faults.

This change is required in order to be able to detect whether a pte
points to a ZERO_PAGE using only its (pte, vaddr) pair.

Signed-off-by: Nick Piggin <npiggin@suse.de>

Index: linux-2.6/mm/mremap.c
===================================================================
--- linux-2.6.orig/mm/mremap.c
+++ linux-2.6/mm/mremap.c
@@ -141,6 +141,10 @@ move_one_page(struct vm_area_struct *vma
 			if (dst) {
 				pte_t pte;
 				pte = ptep_clear_flush(vma, old_addr, src);
+				/* ZERO_PAGE can be dependant on virtual addr */
+				if (pfn_valid(pte_pfn(pte)) &&
+					pte_page(pte) == ZERO_PAGE(old_addr))
+					pte = pte_wrprotect(mk_pte(ZERO_PAGE(new_addr), new_vma->vm_page_prot));
 				set_pte_at(mm, new_addr, dst, pte);
 			} else
 				error = -ENOMEM;

  reply	other threads:[~2005-07-26  8:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  8:15 [patch 0/6] remove PageReserved Nick Piggin
2005-07-26  8:16 ` [patch 1/6] mm: comment rmap Nick Piggin
2005-07-26  8:17   ` [patch 2/6] mm: micro-optimise rmap Nick Piggin
2005-07-26  8:18     ` [patch 3/6] mm: cleanup rmap Nick Piggin
2005-07-26  8:19       ` [patch 4/6] mm: remove atomic Nick Piggin
2005-07-26  8:20         ` Nick Piggin [this message]
2005-07-26  8:20           ` [patch 6/6] mm: core remove PageReserved Nick Piggin
2005-07-26  8:56             ` [patch 6/6] mm: core remove PageReserved (take 2) Nick Piggin
2005-07-27 11:30     ` [patch 2/6] mm: micro-optimise rmap Alexander Nyberg
2005-07-28  0:53       ` Nick Piggin
2005-07-26  8:21 ` [patch 0/6] remove PageReserved Nick Piggin
2005-07-26 13:09 ` Kumar Gala
2005-07-27  0:22   ` Nick Piggin

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=42E5F238.4020302@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.