From: Christoph Lameter <cl@linux.com>
To: Hugh Dickins <hughd@google.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: 4.12-rc ppc64 4k-page needs costly allocations
Date: Thu, 1 Jun 2017 10:31:03 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1706011027310.8835@east.gentwo.org> (raw)
In-Reply-To: <alpine.LSU.2.11.1705311112290.1839@eggly.anvils>
> > I am curious as to what is going on there. Do you have the output from
> > these failed allocations?
>
> I thought the relevant output was in my mail. I did skip the Mem-Info
> dump, since that just seemed noise in this case: we know memory can get
> fragmented. What more output are you looking for?
The output for the failing allocations when you disabling debugging. For
that I would think that you need remove(!) the slub_debug statement on the kernel
command line. You can verify that debug is off by inspecting the values in
/sys/kernel/slab/<yourcache>/<debug option>
> But it was still order 4 when booted with slub_debug=O, which surprised me.
> And that surprises you too? If so, then we ought to dig into it further.
No it does no longer. I dont think slub_debug=O does disable debugging
(frankly I am not sure what it does). Please do not specify any debug options.
--
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:[~2017-06-01 15:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 19:43 Hugh Dickins
2017-05-31 6:46 ` Michael Ellerman
2017-05-31 14:09 ` Christoph Lameter
2017-05-31 18:44 ` Hugh Dickins
2017-05-31 19:02 ` Mathieu Malaterre
2017-06-01 15:31 ` Christoph Lameter [this message]
2017-06-01 17:22 ` Hugh Dickins
2017-06-01 18:16 ` Christoph Lameter
2017-06-01 18:37 ` Hugh Dickins
2017-06-02 3:09 ` Michael Ellerman
2017-06-02 4:00 ` Hugh Dickins
2017-06-02 14:33 ` Christoph Lameter
2017-06-08 5:44 ` Michael Ellerman
2017-06-02 14:32 ` Christoph Lameter
2017-06-08 5:52 ` Michael Ellerman
2017-05-31 14:06 ` Christoph Lameter
2017-06-01 4:19 ` Aneesh Kumar K.V
2017-06-01 16:57 ` Hugh Dickins
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.1706011027310.8835@east.gentwo.org \
--to=cl@linux.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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