From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] do not count pages in holes with sparsemem
Date: Thu, 27 Jul 2006 11:00:25 +0200 [thread overview]
Message-ID: <44C880A9.1070402@innova-card.com> (raw)
In-Reply-To: <20060727.002153.41632148.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
> On Wed, 26 Jul 2006 16:33:45 +0200, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
>> I don't think that's correct to mark them as "reserved". Basicaly
>> "reserved" means that it belongs to the kernel (code or data), these
>> holes are not and we will end up to have wrong value as you pointed
>> out.
>>
>> Having quick look at sparsemem code, I don't think that it expects
>> to have holes inside a section, do it ? If so you probably have to
>> fix up your section size...
>
> Yes, for such small holes, sparsemem and flatmem is same. We can use
> smaller section size to save more memory, but I suppose it will be a
> bit slower.
>
I'm suprised that sparsemem code doens't check for holes inside
sections. I would feel really more confortable to use sparsemem if a
check like the following patch exists. We could safely use pfn_valid()
in _any_ cases and if holes exist inside sections then the user have
to fix up its section sizes.
what do you think ?
Franck
-- >8 --
diff --git a/mm/sparse.c b/mm/sparse.c
index 86c52ab..4c29a13 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -119,6 +119,13 @@ void memory_present(int nid, unsigned lo
{
unsigned long pfn;
+ if (start & (PAGES_PER_SECTION-1) || end & (PAGES_PER_SECTION-1)) {
+ printk(KERN_ERR "SPARSEMEM: memory area (%lx-%lx) creates a "
+ "hole inside a section, fix your SECTION_SIZE_BITS "
+ "value...\n", start, end);
+ BUG();
+ }
+
start &= PAGE_SECTION_MASK;
for (pfn = start; pfn < end; pfn += PAGES_PER_SECTION) {
unsigned long section = pfn_to_section_nr(pfn);
next prev parent reply other threads:[~2006-07-27 9:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 13:13 [PATCH] do not count pages in holes with sparsemem Atsushi Nemoto
2006-07-05 13:58 ` Franck Bui-Huu
2006-07-05 14:17 ` Atsushi Nemoto
2006-07-06 13:12 ` Franck Bui-Huu
2006-07-06 14:36 ` Atsushi Nemoto
2006-07-06 14:59 ` Franck Bui-Huu
2006-07-06 15:05 ` Franck Bui-Huu
2006-07-06 15:26 ` Atsushi Nemoto
2006-07-08 14:39 ` Franck Bui-Huu
2006-07-08 16:03 ` Atsushi Nemoto
2006-07-08 16:15 ` Franck Bui-Huu
2006-07-09 12:56 ` Atsushi Nemoto
2006-07-10 11:34 ` Franck Bui-Huu
2006-07-10 14:34 ` Atsushi Nemoto
2006-07-11 8:33 ` Franck Bui-Huu
2006-07-11 13:24 ` Atsushi Nemoto
2006-07-26 14:33 ` Franck Bui-Huu
2006-07-26 15:21 ` Atsushi Nemoto
2006-07-27 9:00 ` Franck Bui-Huu [this message]
2006-07-28 12:48 ` Atsushi Nemoto
2006-09-24 9:48 ` girish
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=44C880A9.1070402@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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