($INBOX_DIR/description missing)
 help / color / Atom feed
From: Kars de Jong <karsdejong@home.nl>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: m68k Kconfig warning
Date: Wed, 4 Dec 2019 12:58:59 +0100
Message-ID: <CACz-3riEr_HFAxQV8aorSqSwCyX9ZutwUqRR0qK8DuWg8ZWsJg@mail.gmail.com> (raw)
In-Reply-To: <20191202160101.GB17203@linux.ibm.com>

Hi Mike!

Op ma 2 dec. 2019 om 17:01 schreef Mike Rapoport <rppt@linux.ibm.com>:
> The patches are here:
> https://www.spinics.net/lists/linux-m68k/msg13588.html
>
> Aside from some technicalities we had troubles deciding what should be the
> section size. With larger section size we might end up with wasted memory
> for memory maps and with smaller section size we'll have to limit the
> addressable physical memory...

I read through that thread. I believe our current page->flags needs 22
bits for the normal FLAGS and 2 bits for the ZONES, which leaves 8
bits for the SECTION. This is what Geert found out (it worked with
MAX_PHYSMEM_BITS = 30 and SECTION_SIZE_BITS = 22).
I think we can reduces ZONES to a single bit. We currently put all
memory in ZONE_DMA, so I think we might just as well put it in
ZONE_NORMAL and disable ZONE_DMA.

That would enable us to have 8 MB sections and use the full 32-bit
address space, correct? That may be a working compromise?

Kind regards,

Kars.

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  1:27 Randy Dunlap
2019-11-27  7:12 ` Geert Uytterhoeven
2019-12-02 11:42   ` Kars de Jong
2019-12-02 13:32     ` Geert Uytterhoeven
2019-12-02 16:01       ` Mike Rapoport
2019-12-04 11:58         ` Kars de Jong [this message]

Reply instructions:

You may reply publically 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=CACz-3riEr_HFAxQV8aorSqSwCyX9ZutwUqRR0qK8DuWg8ZWsJg@mail.gmail.com \
    --to=karsdejong@home.nl \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=rdunlap@infradead.org \
    --cc=rppt@linux.ibm.com \
    /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

($INBOX_DIR/description missing)

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-m68k/0 linux-m68k/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-m68k linux-m68k/ https://lore.kernel.org/linux-m68k \
		linux-m68k@vger.kernel.org linux-m68k@lists.linux-m68k.org
	public-inbox-index linux-m68k

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-m68k


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git