From: Suresh Siddha <suresh.b.siddha@intel.com>
To: hpa@zytor.com, mingo@elte.hu, tglx@linutronix.de,
arjan@linux.jf.intel.com
Cc: linux-kernel@vger.kernel.org, chinang.ma@intel.com
Subject: [patch 0/2] x86_64: preserve large page text mappings with CONFIG_DEBUG_RODATA
Date: Wed, 14 Oct 2009 14:46:54 -0700 [thread overview]
Message-ID: <20091014214654.423040927@sbs-t61.sc.intel.com> (raw)
Most of the distributions enable CONFIG_DEBUG_RODATA by default, with the
assumption that the debug protection checks come with no cost. Our OLTP tests
showed 1% improvement (with 2% reduction in system time and 1% increase in
iowait idle time) by disabling CONFIG_DEBUG_RODATA on a two socket
NHM-EP system.
CONFIG_DEBUG_RODATA breaks some of the kernel text/data large page
mappings to small pages, thus causing this regression. These two
patches address this issue.
Experiments with EL5 kernel and mainline show that the first patch in the series
(preserve large page mapping for 1st 2MB kernel txt with CONFIG_DEBUG_RODATA)
should recover most of the above mentioned regression. We are doing
couple of more OLTP tests for the confirmation.
thanks,
suresh
next reply other threads:[~2009-10-14 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 21:46 Suresh Siddha [this message]
2009-10-14 21:46 ` [patch 1/2] x86_64: preserve large page mapping for 1st 2MB kernel txt " Suresh Siddha
2009-10-24 1:03 ` [tip:branch?] x86-64: " tip-bot for Suresh Siddha
2009-10-14 21:46 ` [patch 2/2] x86_64: align RODATA kernel section to 2MB " Suresh Siddha
2009-10-15 3:24 ` Sam Ravnborg
2009-10-15 20:23 ` Suresh Siddha
2009-10-24 1:03 ` [tip:branch?] x86-64: " tip-bot for Suresh Siddha
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=20091014214654.423040927@sbs-t61.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=arjan@linux.jf.intel.com \
--cc=chinang.ma@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®