mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akira Takeuchi <takeuchi.akr@jp.panasonic.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] linux: ARM: memmap: Revise freeing unused memmap entries for SPARSEMEM
Date: Fri, 30 Mar 2012 10:27:27 +0900	[thread overview]
Message-ID: <20120330102727.3F01.38390934@jp.panasonic.com> (raw)
In-Reply-To: <20120329121313.GF22414@n2100.arm.linux.org.uk>

On Thu, 29 Mar 2012 13:13:14 +0100
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> On Thu, Mar 29, 2012 at 07:02:52PM +0900, Akira Takeuchi wrote:
> > F0-F4 is the unused memory regions and their corresponding memmap entries
> > can be freed. However, free_unused_memmap() only frees the entries for
> > F1/F2/F4, and does not free the entries for F0/F3.
> 
> No we're not going to support having free areas at the start of an
> otherwise populated bank of memory.  This is just insane.  Fix your
> hardware instead or your sparsemem setup.

As you say, it is able to reduce the number of unused entries remained
by setting SECTION_SIZE_BITS smaller.
On the other hand, I think it's not always true to assign whole memory
to Linux. In some cases, there are free areas at the start of populated
bank of memory and these free areas are assigned to sub CPUs or DSPs
for example. Recent CE SoCs are apt to include multiple CPUs and DSPs
sharing memory among them. This patch is beneficial for such systems,
I think.


Regards,
Akira Takeuchi


      reply	other threads:[~2012-03-30  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 10:01 [PATCH 1/2] linux: sparsemem: Initialize all memmap entries within sections Akira Takeuchi
2012-03-29 10:02 ` [PATCH 2/2] linux: ARM: memmap: Revise freeing unused memmap entries for SPARSEMEM Akira Takeuchi
2012-03-29 12:13   ` Russell King - ARM Linux
2012-03-30  1:27     ` Akira Takeuchi [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=20120330102727.3F01.38390934@jp.panasonic.com \
    --to=takeuchi.akr@jp.panasonic.com \
    --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®