From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: About SECTION_SIZE_BITS for Sparsemem
Date: Wed, 14 Jul 2010 09:49:43 +0100 [thread overview]
Message-ID: <20100714084943.GA9115@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTim55BDz4_vWhTnDVj1EP42MxAMZzP2PR80j5fLN@mail.gmail.com>
On Wed, Jul 14, 2010 at 08:59:06AM +0900, Minchan Kim wrote:
> But I think Kukjin case's best solution is to make section size 16M, not 256M.
> Regardless of this, Your idea is the direction we should proceed, I think.
So what if someone decides to fit 8MB DRAMs to the board?
next prev parent reply other threads:[~2010-07-14 8:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 8:32 About SECTION_SIZE_BITS for Sparsemem Kukjin Kim
2010-07-12 9:35 ` Kyungmin Park
2010-07-12 9:58 ` Kukjin Kim
2010-07-12 10:08 ` Kyungmin Park
2010-07-12 10:13 ` Russell King - ARM Linux
2010-07-12 9:52 ` Minchan Kim
2010-07-12 10:13 ` Kukjin Kim
2010-07-12 10:35 ` Minchan Kim
2010-07-13 0:25 ` KAMEZAWA Hiroyuki
2010-07-13 1:53 ` KAMEZAWA Hiroyuki
2010-07-13 18:31 ` Russell King - ARM Linux
2010-07-13 2:05 ` Minchan Kim
2010-07-13 3:03 ` KAMEZAWA Hiroyuki
2010-07-13 9:28 ` Mel Gorman
2010-07-13 9:38 ` Russell King - ARM Linux
2010-07-13 9:26 ` Mel Gorman
2010-07-13 9:38 ` Russell King - ARM Linux
2010-07-13 9:50 ` Mel Gorman
2010-07-13 17:37 ` Russell King - ARM Linux
2010-07-13 20:32 ` Mel Gorman
2010-07-13 23:59 ` Minchan Kim
2010-07-14 8:49 ` Russell King - ARM Linux [this message]
2010-07-14 11:04 ` Minchan Kim
2010-07-14 20:49 ` Russell King - ARM Linux
2010-07-16 0:07 ` Minchan Kim
2010-07-14 8:59 ` Russell King - ARM Linux
2010-07-14 13:14 ` Mel Gorman
2010-07-12 10:45 ` Russell King - ARM Linux
2010-07-12 12:28 ` Minchan Kim
2010-07-12 12:42 ` Russell King - ARM Linux
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=20100714084943.GA9115@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).