From: Christopher Lameter <cl@linux.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org
Subject: Re: [RFC] Scale slub page allocations with memory size
Date: Wed, 25 Apr 2018 14:13:03 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1804251410100.31137@nuc-kabylake> (raw)
In-Reply-To: <20180425044752.GB15974@bombadil.infradead.org>
On Tue, 24 Apr 2018, Matthew Wilcox wrote:
> From: Matthew Wilcox <mawilcox@microsoft.com>
>
> With larger memory sizes, it's more important to avoid external
> fragmentation than reduce memory usage.
If you do that then the higher order pages that we will then be using will
be exhausted faster. I think we need a generic fix to be able to preserve
higher order pages first.
Dave Hansen and I thought about a 2M basepage configuration?
Something between 4k and 2M would be better but then the hardware wont
support that and given that we can have terabytes in a server this may
be feasable now.
Or make order 0 be 64k page like on ARM 64 and Power and then handle
multiple ptes like the implementation years ago by Hugh.
prev parent reply other threads:[~2018-04-25 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 4:47 Matthew Wilcox
2018-04-25 19:13 ` Christopher Lameter [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=alpine.DEB.2.20.1804251410100.31137@nuc-kabylake \
--to=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox