From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Suleiman Souhlal <ssouhlal@FreeBSD.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Suleiman Souhlal <suleiman@google.com>,
linux-mm <linux-mm@kvack.org>, hugh <hugh@veritas.com>
Subject: [PATCH] mm: avoid dirtying shared mappings on mlock
Date: Fri, 12 Oct 2007 11:03:25 +0200 [thread overview]
Message-ID: <1192179805.27435.6.camel@twins> (raw)
In-Reply-To: <69AF9B2A-6AA7-4078-B0A2-BE3D4914AEDC@FreeBSD.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
Subject: mm: avoid dirtying shared mappings on mlock
Suleiman noticed that shared mappings get dirtied when mlocked.
Avoid this by teaching make_pages_present about this case.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Suleiman Souhlal <suleiman@google.com>
---
mm/memory.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Index: linux-2.6/mm/memory.c
===================================================================
--- linux-2.6.orig/mm/memory.c
+++ linux-2.6/mm/memory.c
@@ -2719,7 +2719,12 @@ int make_pages_present(unsigned long add
vma = find_vma(current->mm, addr);
if (!vma)
return -1;
- write = (vma->vm_flags & VM_WRITE) != 0;
+ /*
+ * We want to touch writable mappings with a write fault in order
+ * to break COW, except for shared mappings because these don't COW
+ * and we would not want to dirty them for nothing.
+ */
+ write = (vma->vm_flags & (VM_WRITE|VM_SHARED)) == VM_WRITE;
BUG_ON(addr >= end);
BUG_ON(end > vma->vm_end);
len = DIV_ROUND_UP(end, PAGE_SIZE) - addr/PAGE_SIZE;
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-12 9:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 23:52 [PATCH] Don't needlessly dirty mlocked pages when initially faulting them in Suleiman Souhlal
2007-07-27 0:23 ` Andrew Morton
2007-07-27 6:33 ` Peter Zijlstra
2007-10-12 6:50 ` Suleiman Souhlal
2007-10-12 9:03 ` Peter Zijlstra [this message]
2007-10-11 16:57 ` [PATCH] mm: avoid dirtying shared mappings on mlock Nick Piggin
2007-10-11 16:57 ` Nick Piggin
2007-10-11 17:07 ` Nick Piggin
2007-10-11 17:07 ` Nick Piggin
2007-10-12 10:37 ` Peter Zijlstra
2007-10-11 18:14 ` Nick Piggin
2007-10-11 18:14 ` Nick Piggin
2007-10-12 10:50 ` Peter Zijlstra
2007-10-12 12:23 ` Nick Piggin
2007-10-12 12:23 ` Nick Piggin
2007-10-12 14:53 ` Arjan van de Ven
2007-10-12 14:53 ` Arjan van de Ven
2007-10-12 14:58 ` Peter Zijlstra
2007-10-12 17:45 ` Suleiman Souhlal
2007-10-12 17:45 ` Suleiman Souhlal
2007-10-12 17:53 ` Arjan van de Ven
2007-10-12 17:53 ` Arjan van de Ven
2007-10-12 18:02 ` Peter Zijlstra
2007-10-12 18:02 ` Peter Zijlstra
2007-10-12 13:10 ` [PATCH] Don't needlessly dirty mlocked pages when initially faulting them in Mauro Giachero
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=1192179805.27435.6.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ssouhlal@FreeBSD.org \
--cc=suleiman@google.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.