From: Matthew Wilcox <willy@infradead.org>
To: Christopher Lameter <cl@linux.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org, akpm@linux-foundation.org,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org,
Thomas Schoebel-Theuer <tst@schoebel-theuer.de>
Subject: Re: [RFC] Protect larger order pages from breaking up
Date: Mon, 12 Feb 2018 09:36:30 -0800 [thread overview]
Message-ID: <20180212173630.GB9396@bombadil.infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1802091311090.3059@nuc-kabylake>
On Fri, Feb 09, 2018 at 01:24:41PM -0600, Christopher Lameter wrote:
> Control over this feature is by writing to /proc/zoneinfo.
>
> F.e. to ensure that 2000 16K pages stay available for jumbo
> frames do
>
> echo "3=2000" >/proc/zoneinfo
That seems ... wrong. 4k is order 0, 8k is order 1, 16k is order 2,
32k is order 3.
> One can then also f.e. operate the slub allocator with
> 64k pages. Specify "slub_max_order=3 slub_min_order=3" on
> the kernel command line and all slab allocator allocations
> will occur in 16K page sizes.
This example also reads weird ;-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-12 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 19:24 [RFC] Protect larger order pages from breaking up Christopher Lameter
2018-02-12 17:36 ` Matthew Wilcox [this message]
2018-02-12 18:37 ` Christopher Lameter
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=20180212173630.GB9396@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=tst@schoebel-theuer.de \
/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;
as well as URLs for NNTP newsgroup(s).