From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Oleg Nesterov'" <oleg@tv-sign.ru>, <linux-kernel@vger.kernel.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Christoph Lameter" <christoph@lameter.com>,
"Andrew Morton" <akpm@osdl.org>
Subject: RE: [PATCH 0/5] timers: description
Date: Thu, 24 Mar 2005 13:56:49 -0800 [thread overview]
Message-ID: <200503242156.j2OLung08187@unix-os.sc.intel.com> (raw)
In-Reply-To: <423ED7E4.2A1F0970@tv-sign.ru>
Oleg Nesterov wrote on Monday, March 21, 2005 6:19 AM
> These patches are updated version of 'del_timer_sync: proof of concept'
> 2 patches.
Looks good performance wise. Took a quick micro benchmark measurement on
a 16-node numa box (32-way). Results are pretty nice (to the expectation).
Time to execute del_timer_sync, averaged over 10,000 call:
Vanilla 2.6.11 19,313 ns
2.6.12-rc1-mm1 81 ns
del_singleshot_timer_sync 74ns
Took another measurement on a 4-way smp box:
Vanilla 2.6.11 648 ns
2.6.12-rc1-mm1 55 ns
del_singleshot 41 ns
And Andrew always asks what are the impact on real-world bench, we did
not see performance regression on db transaction processing benchmark
with these set of timer patches versus using del_singleshot_timer_sync.
(del_singleshot_timer_sync is slightly faster, though 14 ns difference
falls well into noise range)
Note: I've only stress tested deleting an un-expired timer.
next prev parent reply other threads:[~2005-03-24 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 14:19 [PATCH 6/5] timers: enable irqs in __mod_timer() Oleg Nesterov
2005-03-22 5:43 ` Andrew Morton
2005-03-24 21:56 ` Chen, Kenneth W [this message]
2005-03-26 19:52 ` [PATCH 0/5] timers: description Chen, Kenneth W
2005-03-27 10:08 ` Oleg Nesterov
2005-03-28 19:12 ` Christoph Lameter
2005-03-29 11:27 ` Oleg Nesterov
2005-03-29 14:47 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-03-19 18:30 Oleg Nesterov
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=200503242156.j2OLung08187@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
/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®