From: Mel Gorman <mgorman@techsingularity.net>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/Kconfig: make SPARSEMEM default for 32-bit
Date: Wed, 24 Apr 2019 15:19:36 +0100 [thread overview]
Message-ID: <20190424141936.GU18914@techsingularity.net> (raw)
In-Reply-To: <1556112252-9339-2-git-send-email-rppt@linux.ibm.com>
On Wed, Apr 24, 2019 at 04:24:11PM +0300, Mike Rapoport wrote:
> Sparsemem has been a default memory model for x86-64 for over a decade
> since the commit b263295dbffd ("x86: 64-bit, make sparsemem vmemmap the
> only memory model").
>
> Make it the default for 32-bit NUMA systems (if there any left) as well.
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-04-24 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 13:24 [PATCH 0/2] x86/Kconfig: deprecate DISCONTIGMEM support for 32-bit Mike Rapoport
2019-04-24 13:24 ` [PATCH 1/2] x86/Kconfig: make SPARSEMEM default " Mike Rapoport
2019-04-24 14:19 ` Mel Gorman [this message]
2019-04-25 7:32 ` [tip:x86/mm] x86/Kconfig: Make SPARSEMEM default for 32-bit x86 tip-bot for Mike Rapoport
2019-04-24 13:24 ` [PATCH 2/2] x86/Kconfig: deprecate DISCONTIGMEM support for 32-bit Mike Rapoport
2019-04-24 14:20 ` Mel Gorman
2019-04-25 7:33 ` [tip:x86/mm] x86/Kconfig: Deprecate DISCONTIGMEM support for 32-bit x86 tip-bot for 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=20190424141936.GU18914@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@kernel.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.