From: Pavel Emelyanov <xemul@parallels.com>
To: Linux MM <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [PATCH 2/3] mincore: Introduce the MINCORE_ANON bit
Date: Mon, 26 Dec 2011 00:46:17 +0400 [thread overview]
Message-ID: <4EF78B99.1020109@parallels.com> (raw)
In-Reply-To: <4EF78B6A.8020904@parallels.com>
When creating a memory dump of a running application it is better to have
the smallest possible set of pages. Using the existing mincore() bit helps,
but not much -- it repotes pages from page cache, which have not necessarily
being mapped by an application, and pages from private file mappings, that
are not yet being cow-ed and thus their contents doesn't differ from file.
Introduce the 2nd bit of mincore, that reports whether a page is not backed
by a file on disk. I.e. all pages from anonymous mappings and those pages
from private file mappings, that have already being cow-ed by write.
Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
---
include/linux/mman.h | 1 +
mm/mincore.c | 15 +++++++++++++--
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/include/linux/mman.h b/include/linux/mman.h
index e4fda1e..9d1de16 100644
--- a/include/linux/mman.h
+++ b/include/linux/mman.h
@@ -11,6 +11,7 @@
#define OVERCOMMIT_NEVER 2
#define MINCORE_RESIDENT 0x1
+#define MINCORE_ANON 0x2
#ifdef __KERNEL__
#include <linux/mm.h>
diff --git a/mm/mincore.c b/mm/mincore.c
index b719cdd..3163dfb 100644
--- a/mm/mincore.c
+++ b/mm/mincore.c
@@ -38,7 +38,7 @@ static void mincore_hugetlb_page_range(struct vm_area_struct *vma,
addr & huge_page_mask(h));
present = ptep && !huge_pte_none(huge_ptep_get(ptep));
while (1) {
- *vec = (present ? MINCORE_RESIDENT : 0);
+ *vec = (present ? MINCORE_RESIDENT : 0) | MINCORE_ANON;
vec++;
addr += PAGE_SIZE;
if (addr == end)
@@ -86,6 +86,17 @@ static unsigned char mincore_page(struct address_space *mapping, pgoff_t pgoff)
return present ? MINCORE_RESIDENT : 0;
}
+static unsigned char mincore_pte(struct vm_area_struct *vma, unsigned long addr, pte_t pte)
+{
+ struct page *pg;
+
+ pg = vm_normal_page(vma, addr, pte);
+ if (!pg)
+ return 0;
+ else
+ return PageAnon(pg) ? MINCORE_ANON : 0;
+}
+
static void mincore_unmapped_range(struct vm_area_struct *vma,
unsigned long addr, unsigned long end,
unsigned char *vec)
@@ -122,7 +133,7 @@ static void mincore_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
if (pte_none(pte))
mincore_unmapped_range(vma, addr, next, vec);
else if (pte_present(pte))
- *vec = MINCORE_RESIDENT;
+ *vec = MINCORE_RESIDENT | mincore_pte(vma, addr, pte);
else if (pte_file(pte)) {
pgoff = pte_to_pgoff(pte);
*vec = mincore_page(vma->vm_file->f_mapping, pgoff);
--
1.5.5.6
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-25 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 20:45 [RFC][PATCH 0/3] Extend the mincore() report bits Pavel Emelyanov
2011-12-25 20:45 ` [PATCH 1/3] mincore: Introduce named constant for existing bit Pavel Emelyanov
2011-12-25 20:46 ` Pavel Emelyanov [this message]
2011-12-26 0:05 ` [PATCH 2/3] mincore: Introduce the MINCORE_ANON bit KOSAKI Motohiro
2011-12-26 16:07 ` Pavel Emelyanov
2011-12-26 16:35 ` KOSAKI Motohiro
2011-12-26 16:49 ` Pavel Emelyanov
2011-12-27 22:53 ` KOSAKI Motohiro
2011-12-25 20:46 ` [PATCH 3/3] mincore: Introduce the MINCORE_SWAP bit Pavel Emelyanov
2011-12-26 8:08 ` Konstantin Khlebnikov
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=4EF78B99.1020109@parallels.com \
--to=xemul@parallels.com \
--cc=aarcange@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox