From: Christian Borntraeger <borntraeger@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
x86@kernel.org, Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [PATCH/RFC 0/3] Optimize CONFIG_DEBUG_PAGEALLOC
Date: Tue, 26 Jan 2016 10:18:22 +0100 [thread overview]
Message-ID: <1453799905-10941-1-git-send-email-borntraeger@de.ibm.com> (raw)
As CONFIG_DEBUG_PAGEALLOC can be enabled/disabled via kernel
parameters we can optimize some cases by checking the enablement
state.
I have done s390 and x86 as examples. Other architecture can
provide followup patches later on.
Christian Borntraeger (3):
mm: provide debug_pagealloc_enabled() without CONFIG_DEBUG_PAGEALLOC
x86: query dynamic DEBUG_PAGEALLOC setting
s390: query dynamic DEBUG_PAGEALLOC setting
arch/s390/kernel/dumpstack.c | 4 +++-
arch/s390/mm/vmem.c | 10 ++++------
arch/x86/kernel/dumpstack.c | 4 +++-
arch/x86/mm/init.c | 7 ++++---
arch/x86/mm/pageattr.c | 14 ++++----------
include/linux/mm.h | 4 ++++
6 files changed, 22 insertions(+), 21 deletions(-)
--
2.3.0
--
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 reply other threads:[~2016-01-26 9:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 9:18 Christian Borntraeger [this message]
2016-01-26 9:18 ` [PATCH/RFC 1/3] mm: provide debug_pagealloc_enabled() without CONFIG_DEBUG_PAGEALLOC Christian Borntraeger
2016-01-26 23:23 ` David Rientjes
2016-01-26 9:18 ` [PATCH/RFC 2/3] x86: query dynamic DEBUG_PAGEALLOC setting Christian Borntraeger
2016-01-26 9:18 ` [PATCH/RFC 3/3] s390: " Christian Borntraeger
2016-01-26 18:19 ` Heiko Carstens
2016-01-26 20:38 ` Thomas Gleixner
2016-01-26 23:29 ` David Rientjes
2016-01-27 0:19 ` Joonsoo Kim
2016-01-27 0:36 ` David Rientjes
2016-01-27 0:59 ` Joonsoo Kim
2016-01-27 7:59 ` Christian Borntraeger
2016-01-27 12:41 ` Vlastimil Babka
2016-01-27 12:47 ` Christian Borntraeger
2016-01-27 13:03 ` Vlastimil Babka
2016-01-27 13:09 ` Christian Borntraeger
2016-01-28 4:25 ` Joonsoo Kim
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=1453799905-10941-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox