From: dave@linux.vnet.ibm.com (Dave Hansen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: Regarding section when dealing with meminfo
Date: Mon, 24 Jan 2011 10:47:37 -0800 [thread overview]
Message-ID: <1295894857.11047.556.camel@nimitz> (raw)
In-Reply-To: <20110124175807.GA27427@n2100.arm.linux.org.uk>
On Mon, 2011-01-24 at 17:58 +0000, Russell King - ARM Linux wrote:
> Wrong. For flatmem, we have a pfn_valid() which is backed by doing a
> one, two or maybe rarely three compare search of the memblocks. Short
> of having a bitmap of every page in the 4GB memory space, you can't
> get more efficient than that.
Sweet. So, we can just take the original patch that started this
conversation, add the requisite pfn_valid()s and pfn_to_page()s, and
skip the sparsemem #ifdefs. Right?
-- Dave
next prev parent reply other threads:[~2011-01-24 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 9:45 [PATCH] ARM: mm: Regarding section when dealing with meminfo KyongHo Cho
2011-01-20 14:28 ` Minchan Kim
2011-01-20 17:25 ` Dave Hansen
[not found] ` <AANLkTinXAiShaf1f69ufVHg7KPaY5j=jmOTtK71GNNp5@mail.gmail.com>
[not found] ` <AANLkTikBbknwsLvN-b4HVqL_gAUHC-4VjQ=WQ=h_kLhW@mail.gmail.com>
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 [this message]
2011-01-25 0:33 ` KyongHo Cho
2011-01-21 2:12 ` KyongHo Cho
2011-01-21 10:38 ` Russell King - ARM Linux
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=1295894857.11047.556.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--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