From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, clameter@engr.sgi.com, apw@shadowen.org
Subject: [RFC][PATCH] vmemmap on sparsemem v2 [4/5] optimized pfn_valid
Date: Tue, 5 Dec 2006 22:09:06 +0900 [thread overview]
Message-ID: <20061205220906.f1d24dfc.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20061205214517.5ad924f6.kamezawa.hiroyu@jp.fujitsu.com>
This implements pfn_valid() as ia64's vmem_map does.
This eliminates access to mem_section[] array by usual ops.
Because vmemmap on sparsemem is aligned. access check function can be easier
than ia64's.
Signed-Off-By: KAMEZAWA Hiruyoki <kamezawa.hiroyu@jp.fujitsu.com>
include/linux/mmzone.h | 14 ++++++++++++++
mm/sparse.c | 23 +++++++++++++++++++++++
2 files changed, 37 insertions(+)
Index: devel-2.6.19-rc6-mm2/include/linux/mmzone.h
===================================================================
--- devel-2.6.19-rc6-mm2.orig/include/linux/mmzone.h 2006-12-05 21:25:43.000000000 +0900
+++ devel-2.6.19-rc6-mm2/include/linux/mmzone.h 2006-12-05 21:45:21.000000000 +0900
@@ -752,12 +752,27 @@
return __nr_to_section(pfn_to_section_nr(pfn));
}
+#if defined(SPARSEMEM_VMEM_MAP) && defined(CONFIG_USE_OPT_PFN_VALID)
+/*
+ * Uses hardware assist instead of mem_section[] table walking.
+ * good for SPARSEMEM_EXTREME
+ * To use this, you may need arch support in page fault handler.
+ */
+static inline int pfn_valid(unsigned long pfn)
+{
+ struct page *pg = pfn_to_page(pfn);
+ return (VIRTUAL_MEM_MAP <= pg &&
+ pg < (VIRUTAL_MEM_MAP + VIRTUAL_MEM_MAP_SIZE) &&
+ check_valid_memmap(pg));
+}
+#else
static inline int pfn_valid(unsigned long pfn)
{
if (pfn_to_section_nr(pfn) >= NR_MEM_SECTIONS)
return 0;
return valid_section(__nr_to_section(pfn_to_section_nr(pfn)));
}
+#endif
/*
* These are _only_ used during initialisation, therefore they
Index: devel-2.6.19-rc6-mm2/mm/sparse.c
===================================================================
--- devel-2.6.19-rc6-mm2.orig/mm/sparse.c 2006-12-05 21:25:43.000000000 +0900
+++ devel-2.6.19-rc6-mm2/mm/sparse.c 2006-12-05 21:47:21.000000000 +0900
@@ -103,6 +103,22 @@
#ifdef CONFIG_SPARSEMEM_VMEMMAP
+#ifdef CONFIG_USE_OPT_PFN_VALID
+
+/* check mem_map is valid or not by accessing it.
+ Because virtual mem_map/sparse mem is always alined, just __get_user()
+ check is necessary.
+ */
+int check_valid_memmap(struct page *pg)
+{
+ char byte;
+ if (__get_user(byte, (char __user*)pg) == 0)
+ return 1;
+ return 0;
+}
+
+EXPORT_SYMBOL(check_valid_memmap);
+#endif
static void* __meminit pte_alloc_vmem_map(int node)
{
--
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:[~2006-12-05 13:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 12:45 [RFC][PATCH] vmemmap on sparsemem v2 KAMEZAWA Hiroyuki
2006-12-05 12:49 ` [RFC][PATCH] vmemmap on sparsemem v2 [1/5] generic vmemmap on sparsemem KAMEZAWA Hiroyuki
2006-12-06 18:13 ` Heiko Carstens
2006-12-06 18:17 ` Christoph Lameter
2006-12-07 0:20 ` KAMEZAWA Hiroyuki
2006-12-07 0:20 ` Christoph Lameter
2006-12-07 10:11 ` Heiko Carstens
2006-12-07 10:50 ` KAMEZAWA Hiroyuki
2006-12-07 10:06 ` Heiko Carstens
2006-12-07 10:17 ` KAMEZAWA Hiroyuki
2006-12-08 3:06 ` KAMEZAWA Hiroyuki
2006-12-05 12:53 ` [RFC][PATCH] vmemmap on sparsemem v2 [2/5] memory hotplug support KAMEZAWA Hiroyuki
2006-12-05 12:59 ` [RFC][PATCH] vmemmap on sparsemem v2 [3/5] ia64 vmemamp on sparsemem KAMEZAWA Hiroyuki
2006-12-08 1:09 ` KAMEZAWA Hiroyuki
2006-12-05 13:09 ` KAMEZAWA Hiroyuki [this message]
2006-12-05 13:10 ` [RFC][PATCH] vmemmap on sparsemem v2 [5/5] optimzied pfn_valid support for ia64 KAMEZAWA Hiroyuki
2006-12-10 13:37 ` [RFC][PATCH] vmemmap on sparsemem v2 Andy Whitcroft
2006-12-10 15:19 ` Heiko Carstens
2006-12-11 1:09 ` KAMEZAWA Hiroyuki
2006-12-11 17:23 ` Christoph Lameter
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=20061205220906.f1d24dfc.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=apw@shadowen.org \
--cc=clameter@engr.sgi.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