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, 24 Feb 2006 02:30:35 +0000 [thread overview]
Message-ID: <200602240230.k1O2UZg05919@unix-os.sc.intel.com> (raw)
Here is a respin of previously posted patches 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-02-24 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 2:30 Chen, Kenneth W [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-13 17:01 [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=200602240230.k1O2UZg05919@unix-os.sc.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