From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 0/2] remove per-cpu dtr requirement
Date: Fri, 13 Oct 2006 17:01:33 +0000 [thread overview]
Message-ID: <000001c6eee9$3d10ce20$ff0da8c0@amr.corp.intel.com> (raw)
Christoph's variable kernel page size support patch reminds me
this 10 month old patch:
http://marc.theaimsgroup.com/?l=linux-ia64&m\x114074826111970&w=2
I strongly believe it is stable enough for 2.6.19. Reposted here
for mainline consideration.
----
Patch set that remove pinned DTR per-cpu TLB requirement. Instead
we use DTC to map that translation.
With these two patches, we measured substantial performance gain
on a database benchmark, in the vicinity of 1.6%. I've also done
extensive performance measurement on two other industry standard
benchmarks (cpu, java), and have found to have small gain on those
workloads.
Detail description in the follow on patches.
- Ken
next reply other threads:[~2006-10-13 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 17:01 Chen, Kenneth W [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-24 2:30 [patch 0/2] remove per-cpu dtr requirement Chen, Kenneth W
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='000001c6eee9$3d10ce20$ff0da8c0@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.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