From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch][rfc] optimise resched, idle task
Date: Sun, 03 Apr 2005 23:27:45 +1000 [thread overview]
Message-ID: <424FEF51.9020104@yahoo.com.au> (raw)
In-Reply-To: <424E11C6.8090702@yahoo.com.au>
Nick Piggin wrote:
> This actually improves performance noticably (ie. a % or so) on schedule /
> wakeup happy benchmarks (tbench, on a dual Xeon with HT using mwait idle).
>
Here are some numbers on a 2 socket Xeon with HT and mwait idle.
Average of 3 runs, tbench, single client and single server processes on:
samethread samecpu othercpu
before patch: 188.684 MB/s 189.237 MB/s 172.306 MB/s
after patch : 188.425 MB/s 191.628 MB/s 174.224 MB/s
The improvement on other CPUs should be due to the removal of
RMW operations in resched_task.
prev parent reply other threads:[~2005-04-03 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 3:30 [patch][rfc] optimise resched, idle task Nick Piggin
2005-04-03 13:27 ` Nick Piggin [this message]
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=424FEF51.9020104@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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