From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Minchan Kim' <minchan.kim@gmail.com>,
'Dave Hansen' <dave@linux.vnet.ibm.com>,
'Johannes Weiner' <hannes@cmpxchg.org>,
linux@arm.linux.org.uk, 'Yinghai Lu' <yinghai@kernel.org>,
"'H. Peter Anvin'" <hpa@zytor.com>,
'Andrew Morton' <akpm@linux-foundation.org>,
'Shaohua Li' <shaohua.li@intel.com>,
'Yakui Zhao' <yakui.zhao@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
arm-kernel@lists.infradead.org, 'Mel Gorman' <mel@csn.ul.ie>
Subject: Re: [RFC] Tight check of pfn_valid on sparsemem
Date: Wed, 14 Jul 2010 17:09:48 +0900 [thread overview]
Message-ID: <20100714170948.3eac9132.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <000e01cb2329$3d8c5770$b8a50650$%kim@samsung.com>
On Wed, 14 Jul 2010 16:50:25 +0900
Kukjin Kim <kgene.kim@samsung.com> wrote:
> KAMEZAWA Hiroyuki wrote:
> >
> > On Wed, 14 Jul 2010 01:44:23 +0900
> > Minchan Kim <minchan.kim@gmail.com> wrote:
> >
> > > > If you _really_ can't make the section size smaller, and the vast
> > > > majority of the sections are fully populated, you could hack something
> > > > in. We could, for instance, have a global list that's mostly readonly
> > > > which tells you which sections need to be have their sizes closely
> > > > inspected. That would work OK if, for instance, you only needed to
> > > > check a couple of memory sections in the system. It'll start to suck
> if
> > > > you made the lists very long.
> > >
> > > Thanks for advise. As I say, I hope Russell accept 16M section.
> > >
> Hi,
>
> Thanks for your inputs.
> >
> > It seems what I needed was good sleep....
> > How about this if 16M section is not acceptable ?
> >
> > == NOT TESTED AT ALL, EVEN NOT COMPILED ==
>
> Yeah...
>
> Couldn't build with s5pv210_defconfig when used mmotm tree,
> And couldn't apply your patch against latest mainline 35-rc5.
>
> Could you please remake your patch against mainline 35-rc5?
> Or...please let me know how I can test on my board(smdkv210).
>
Ahh..how brave you are.
my patch was against mmotm-07-01.
select SPARSEMEM_HAS_PIT in config.
(in menuconfig it will appear under Processor type and features.)
This is a fixed one, maybe mm/sparce.o can be compiled.
At least, arch-generic part is compiled.
(This config should be selected automatically via arm's config.
this patch is just for test.)
Signed-off-by: KAMEZAWA hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
arch/arm/mm/init.c | 11 ++++++++++-
include/linux/mmzone.h | 19 ++++++++++++++++++-
mm/Kconfig | 5 +++++
mm/sparse.c | 38 +++++++++++++++++++++++++++++++++++++-
4 files changed, 70 insertions(+), 3 deletions(-)
Index: mmotm-2.6.35-0701/include/linux/mmzone.h
===================================================================
--- mmotm-2.6.35-0701.orig/include/linux/mmzone.h
+++ mmotm-2.6.35-0701/include/linux/mmzone.h
@@ -1047,11 +1047,28 @@ static inline struct mem_section *__pfn_
return __nr_to_section(pfn_to_section_nr(pfn));
}
+#ifdef CONFIG_SPARSEMEM_HAS_PIT
+void mark_memmap_pit(unsigned long start, unsigned long end, bool valid);
+static inline int page_valid(struct mem_section *ms, unsigned long pfn)
+{
+ struct page *page = pfn_to_page(pfn);
+ struct page *__pg = virt_to_page(page);
+ return __pg->private == ms;
+}
+#else
+static inline int page_valid(struct mem_section *ms, unsigned long pfn)
+{
+ return 1;
+}
+#endif
+
static inline int pfn_valid(unsigned long pfn)
{
+ struct mem_section *ms;
if (pfn_to_section_nr(pfn) >= NR_MEM_SECTIONS)
return 0;
- return valid_section(__nr_to_section(pfn_to_section_nr(pfn)));
+ ms = __nr_to_section(pfn_to_section_nr(pfn));
+ return valid_section(ms) && page_valid(ms, pfn);
}
static inline int pfn_present(unsigned long pfn)
Index: mmotm-2.6.35-0701/mm/sparse.c
===================================================================
--- mmotm-2.6.35-0701.orig/mm/sparse.c
+++ mmotm-2.6.35-0701/mm/sparse.c
@@ -13,7 +13,6 @@
#include <asm/dma.h>
#include <asm/pgalloc.h>
#include <asm/pgtable.h>
-
/*
* Permanent SPARSEMEM data:
*
@@ -615,6 +614,43 @@ void __init sparse_init(void)
free_bootmem(__pa(usemap_map), size);
}
+#ifdef CONFIG_SPARSEMEM_HAS_PIT
+/*
+ * Fill memmap's pg->private with a pointer to mem_section.
+ * pfn_valid() will check this later. (see include/linux/mmzone.h)
+ * The caller should call
+ * mark_memmap_pit(start, end, true) # for all allocated mem_map
+ * and, after that,
+ * mark_memmap_pit(start, end, false) # for all pits in mem_map.
+ * please see usage in ARM.
+ */
+void mark_memmap_pit(unsigned long start, unsigned long end, bool valid)
+{
+ struct mem_section *ms;
+ unsigned long pos, next;
+ struct page *pg;
+ void *memmap, *mapend;
+
+ for (pos = start;
+ pos < end; pos = next) {
+ next = (pos + PAGES_PER_SECTION) & PAGE_SECTION_MASK;
+ ms = __pfn_to_section(pos);
+ if (!valid_section(ms))
+ continue;
+ for (memmap = (void*)pfn_to_page(pos),
+ mapend = pfn_to_page(next-1); /* the last page in section*/
+ memmap < mapend;
+ memmap += PAGE_SIZE) {
+ pg = virt_to_page(memmap);
+ if (valid)
+ pg->private = (unsigned long)ms;
+ else
+ pg->private = 0;
+ }
+ }
+}
+#endif
+
#ifdef CONFIG_MEMORY_HOTPLUG
#ifdef CONFIG_SPARSEMEM_VMEMMAP
static inline struct page *kmalloc_section_memmap(unsigned long pnum, int nid,
Index: mmotm-2.6.35-0701/arch/arm/mm/init.c
===================================================================
--- mmotm-2.6.35-0701.orig/arch/arm/mm/init.c
+++ mmotm-2.6.35-0701/arch/arm/mm/init.c
@@ -234,6 +234,13 @@ static void __init arm_bootmem_free(stru
arch_adjust_zones(zone_size, zhole_size);
free_area_init_node(0, zone_size, min, zhole_size);
+
+#ifdef CONFIG_SPARSEMEM
+ for_each_bank(i, mi) {
+ mark_memmap_pit(bank_start_pfn(mi->bank[i]),
+ bank_end_pfn(mi->bank[i]), true);
+ }
+#endif
}
#ifndef CONFIG_SPARSEMEM
@@ -386,8 +393,10 @@ free_memmap(unsigned long start_pfn, uns
* If there are free pages between these,
* free the section of the memmap array.
*/
- if (pg < pgend)
+ if (pg < pgend) {
+ mark_memap_pit(pg >> PAGE_SHIFT, pgend >> PAGE_SHIFT, false);
free_bootmem(pg, pgend - pg);
+ }
}
/*
Index: mmotm-2.6.35-0701/mm/Kconfig
===================================================================
--- mmotm-2.6.35-0701.orig/mm/Kconfig
+++ mmotm-2.6.35-0701/mm/Kconfig
@@ -128,6 +128,11 @@ config SPARSEMEM_VMEMMAP
pfn_to_page and page_to_pfn operations. This is the most
efficient option when sufficient kernel resources are available.
+config SPAESEMEM_HAS_PIT
+ bool "allow holes in sparsemem's memmap"
+ depends on SPARSEMEM && !SPARSEMEM_VMEMMAP
+ default n
+
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
bool "Allow for memory hot-add"
--
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:[~2010-07-14 8:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:53 Minchan Kim
2010-07-12 23:59 ` Kukjin Kim
2010-07-13 3:19 ` KAMEZAWA Hiroyuki
2010-07-13 4:11 ` Minchan Kim
2010-07-13 4:23 ` KAMEZAWA Hiroyuki
2010-07-13 6:04 ` Minchan Kim
2010-07-13 6:40 ` KAMEZAWA Hiroyuki
2010-07-13 8:06 ` Minchan Kim
2010-07-13 8:03 ` KAMEZAWA Hiroyuki
2010-07-13 7:20 ` Russell King - ARM Linux
2010-07-13 7:34 ` KAMEZAWA Hiroyuki
2010-07-13 7:58 ` KAMEZAWA Hiroyuki
2010-07-13 8:02 ` KAMEZAWA Hiroyuki
2010-07-13 18:39 ` Russell King - ARM Linux
2010-07-13 20:46 ` Dave Hansen
2010-07-13 9:30 ` Johannes Weiner
2010-07-13 15:43 ` Minchan Kim
2010-07-13 16:35 ` Dave Hansen
2010-07-13 16:44 ` Minchan Kim
2010-07-14 0:23 ` KAMEZAWA Hiroyuki
2010-07-14 6:44 ` Minchan Kim
2010-07-14 7:10 ` KAMEZAWA Hiroyuki
2010-07-14 7:35 ` Minchan Kim
2010-07-14 7:39 ` KAMEZAWA Hiroyuki
2010-07-14 7:50 ` Kukjin Kim
2010-07-14 8:09 ` KAMEZAWA Hiroyuki [this message]
2010-07-13 9:37 ` Mel Gorman
2010-07-13 9:46 ` Russell King - ARM Linux
2010-07-13 10:00 ` Mel Gorman
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=20100714170948.3eac9132.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=arm-kernel@lists.infradead.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=shaohua.li@intel.com \
--cc=yakui.zhao@intel.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox