LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: KyongHo Cho <pullip.cho@samsung.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
Kukjin Kim <kgene.kim@samsung.com>,
KeyYoung Park <keyyoung.park@samsung.com>,
linux-kernel@vger.kernel.org, Ilho Lee <ilho215.lee@samsung.com>,
linux-mm@kvack.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mm: Regarding section when dealing with meminfo
Date: Fri, 21 Jan 2011 10:38:50 +0000 [thread overview]
Message-ID: <20110121103850.GI13235@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTimsL8YfSdXCBpN2cNVpj8HeJF0f-A7MJQoie+Zm@mail.gmail.com>
On Fri, Jan 21, 2011 at 11:12:27AM +0900, KyongHo Cho wrote:
> Since the size of section is 256 mib and NR_BANKS is defined as 8,
> no ARM system can have more RAM than 2GiB in the current implementation.
> If you want banks in meminfo not to cross sparsemem boundaries,
> we need to find another way of physical memory specification in the kernel.
There is no problem with increasing NR_BANKS.
next prev parent reply other threads:[~2011-01-21 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 9:45 KyongHo Cho
2011-01-20 14:28 ` Minchan Kim
2011-01-20 17:25 ` Dave Hansen
[not found] ` <AANLkTinXAiShaf1f69ufVHg7KPaY5j=jmOTtK71GNNp5@mail.gmail.com>
2011-01-20 17:43 ` Minchan Kim
2011-01-20 17:44 ` Minchan Kim
2011-01-20 17:52 ` KyongHo Cho
2011-01-20 17:20 ` Dave Hansen
[not found] ` <AANLkTi=nsAOtLPK75Wy5Rm8pfWob8xTP5259DyYuxR9J@mail.gmail.com>
2011-01-20 17:48 ` KyongHo Cho
2011-01-20 18:04 ` Dave Hansen
2011-01-20 18:01 ` Russell King - ARM Linux
2011-01-20 18:11 ` Dave Hansen
2011-01-23 18:05 ` Russell King - ARM Linux
2011-01-24 16:52 ` Dave Hansen
2011-01-24 17:58 ` Russell King - ARM Linux
2011-01-24 18:47 ` Dave Hansen
2011-01-25 0:33 ` KyongHo Cho
2011-01-21 2:12 ` KyongHo Cho
2011-01-21 10:38 ` Russell King - ARM Linux [this message]
2011-01-21 11:15 ` KyongHo Cho
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=20110121103850.GI13235@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dave@linux.vnet.ibm.com \
--cc=ilho215.lee@samsung.com \
--cc=keyyoung.park@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pullip.cho@samsung.com \
--subject='Re: [PATCH] ARM: mm: Regarding section when dealing with meminfo' \
/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
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).