From: Johannes Weiner <hannes@cmpxchg.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Mel Gorman <mel@csn.ul.ie>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [rfc patch 1/3] mm: always pass mapping in zap_details
Date: Wed, 30 Sep 2009 23:09:22 +0200 [thread overview]
Message-ID: <1254344964-8124-1-git-send-email-hannes@cmpxchg.org> (raw)
Currently, unmap_mapping_range() only fills in the address space
information in zap details when it wants to filter private COW pages
and the zapping loops need to compare page->mapping against it.
For unmapping private COW pages on truncation, we will need this
information also in the opposite case to filter shared pages.
Demux this one check_mapping member by adding an explicit mode flag
and always pass along the address space.
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Mel Gorman <mel@csn.ul.ie>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
include/linux/mm.h | 3 ++-
mm/memory.c | 11 ++++++-----
2 files changed, 8 insertions(+), 6 deletions(-)
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -732,7 +732,8 @@ extern void user_shm_unlock(size_t, stru
*/
struct zap_details {
struct vm_area_struct *nonlinear_vma; /* Check page->index if set */
- struct address_space *check_mapping; /* Check page->mapping if set */
+ struct address_space *mapping; /* Backing address space */
+ bool keep_private; /* Do not touch private pages */
pgoff_t first_index; /* Lowest page->index to unmap */
pgoff_t last_index; /* Highest page->index to unmap */
spinlock_t *i_mmap_lock; /* For unmap_mapping_range: */
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -824,8 +824,8 @@ static unsigned long zap_pte_range(struc
* invalidate cache without truncating:
* unmap shared but keep private pages.
*/
- if (details->check_mapping &&
- details->check_mapping != page->mapping)
+ if (details->keep_private &&
+ details->mapping != page->mapping)
continue;
/*
* Each page->index must be checked when
@@ -863,7 +863,7 @@ static unsigned long zap_pte_range(struc
continue;
}
/*
- * If details->check_mapping, we leave swap entries;
+ * If details->keep_private, we leave swap entries;
* if details->nonlinear_vma, we leave file entries.
*/
if (unlikely(details))
@@ -936,7 +936,7 @@ static unsigned long unmap_page_range(st
pgd_t *pgd;
unsigned long next;
- if (details && !details->check_mapping && !details->nonlinear_vma)
+ if (details && !details->keep_private && !details->nonlinear_vma)
details = NULL;
BUG_ON(addr >= end);
@@ -2433,7 +2433,8 @@ void unmap_mapping_range(struct address_
hlen = ULONG_MAX - hba + 1;
}
- details.check_mapping = even_cows? NULL: mapping;
+ details.mapping = mapping;
+ details.keep_private = !even_cows;
details.nonlinear_vma = NULL;
details.first_index = hba;
details.last_index = hba + hlen - 1;
--
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 reply other threads:[~2009-09-30 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:09 Johannes Weiner [this message]
2009-09-30 21:09 ` [rfc patch 2/3] mm: serialize truncation unmap against try_to_unmap() Johannes Weiner
2009-09-30 21:09 ` [rfc patch 3/3] mm: munlock COW pages on truncation unmap Johannes Weiner
2009-10-02 2:40 ` KOSAKI Motohiro
2009-10-02 23:38 ` Johannes Weiner
2009-10-03 13:56 ` KOSAKI Motohiro
2009-10-05 19:32 ` Johannes Weiner
2009-10-06 1:11 ` KOSAKI Motohiro
2009-10-06 7:44 ` KOSAKI Motohiro
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=1254344964-8124-1-git-send-email-hannes@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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