All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: linux-m68k@lists.linux-m68k.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Finn Thain <fthain@telegraphics.com.au>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH v3 0/3] m68k/mm: switch from DISCONTIGMEM to SPARSEMEM
Date: Sun, 23 Aug 2020 11:06:49 +0300	[thread overview]
Message-ID: <20200823080649.GH752365@kernel.org> (raw)
In-Reply-To: <28567532-3406-5086-0f77-568af4bbabcf@gmail.com>

On Sun, Aug 23, 2020 at 07:16:45AM +1200, Michael Schmitz wrote:
> Hi Mike,
> 
> Am 22.08.2020 um 21:51 schrieb Mike Rapoport:
> > Hi Michael,
> > 
> > On Sat, Aug 22, 2020 at 11:27:18AM +1200, Michael Schmitz wrote:
> > > Hi Mike,
> > > 
> > > only tested on ARAnyM, but appears to work (after adding sparsemem.h and
> > > changing memblocks_present() to non-static).
> > 
> > Cool, thanks!
> > memblocks_present() is now called from sparse_init() and can be simply
> > dropped.
> 
> Right you are - I missed that in the hurry.
> 
> > 
> > > 20 kB more total memory with sparsemem. Less memory used when booting
> > > to FastRAM, more used when booting to ST-RAM (checked right after boot
> > > on an idle system). The latter probably isn't significant.
> > 
> > When booting to FastRAM we still discard ST-RAM and only use it as
> > device memory for the framebuffer. So the total memory map size will be
> > smaller.
> 
> Makes sense, but I was still surprised that replacing discontigmem by
> sparsemem saves 20 kB regardless of whether or not ST-RAM is used.

The problem with sparse, however, is the memory wasted for empty memmap.
For example, if the section size is 16M and there is, say, 17M of
FastRAM, the memory map will be created for 32M. This means that there
will be 3840 unused 'struct page' objects. :(


> > How many FastRAM do you have in your configuration?
> 
> Only 256 MB. Can't use much more on my old Powerbook.
> 
> Cheers,
> 
> 	Michael
> 

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2020-08-23  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 16:26 [PATCH v3 0/3] m68k/mm: switch from DISCONTIGMEM to SPARSEMEM Mike Rapoport
2020-07-18 16:26 ` [PATCH v3 1/3] m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM Mike Rapoport
2020-07-18 16:26 ` [PATCH v3 2/3] m68k/mm: enable use of generic memory_model.h for !DISCONTIGMEM Mike Rapoport
2020-07-18 16:26 ` [PATCH v3 3/3] m68k/mm: switch from DISCONTIGMEM to SPARSEMEM Mike Rapoport
2020-08-20 16:03 ` [PATCH v3 0/3] " Mike Rapoport
2020-08-20 22:29   ` Michael Schmitz
2020-08-21  7:56     ` Mike Rapoport
2020-08-21 20:58       ` Michael Schmitz
2020-08-21 23:27       ` Michael Schmitz
2020-08-22  9:51         ` Mike Rapoport
2020-08-22 19:16           ` Michael Schmitz
2020-08-23  8:06             ` Mike Rapoport [this message]
2020-08-24 20:47               ` Michael Schmitz
2020-08-25  5:42                 ` Mike Rapoport

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=20200823080649.GH752365@kernel.org \
    --to=rppt@kernel.org \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=rppt@linux.ibm.com \
    --cc=schmitzmic@gmail.com \
    --cc=schwab@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.