From: Min-Hua Chen <orca.chen@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm: improve non-section-aligned low memory mapping
Date: Fri, 8 May 2015 00:20:32 +0800 [thread overview]
Message-ID: <20150507162032.GB6188@debian777.Home> (raw)
In-Reply-To: <20150506103249.GG2067@n2100.arm.linux.org.uk>
On Wed, May 06, 2015 at 11:32:49AM +0100, Russell King - ARM Linux wrote:
> On Sun, Apr 26, 2015 at 04:47:08PM +0800, Min-Hua Chen wrote:
> > @@ -1384,6 +1351,15 @@ static void __init map_lowmem(void)
> > create_mapping(&map);
> > }
> > }
> > +
> > + /*
> > + * Find the first section-aligned memblock and set
> > + * memblock_limit at it.
> > + */
> > + if (!section_memblock_limit && !(end & ~SECTION_MASK)) {
> > + section_memblock_limit = end;
> > + memblock_set_current_limit(section_memblock_limit);
> > + }
>
> I've suggested an alternative solution to this (which just means changing
> the alignment of the memblock limit to 2x SECTION_SIZE).
Sorry I do not understand your suggestion very well. Do you mean the
alignment check should be 2X SECTION_SIZE?
if (!section_memblock_limit && !(end & (2 * SECTION_SIZE - 1))) {
I found that this solution is based on the fact that the first memory block is
always SECTION_SIZE-aligned. So we do not have to check the
alignment of the first memblock:
if (!section_memblock_limit)) {
section_memblock_limit = end;
memblock_set_current_limit(section_memblock_limit);
}
> --
> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
> according to speedtest.net.
prev parent reply other threads:[~2015-05-07 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 8:47 Min-Hua Chen
2015-05-06 10:32 ` Russell King - ARM Linux
2015-05-07 16:20 ` Min-Hua Chen [this message]
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=20150507162032.GB6188@debian777.Home \
--to=orca.chen@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®