From: Tim Chen <tim.c.chen@linux.intel.com>
To: Con Kolivas <ckolivas@gmail.com>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
kernel@kolivas.org, wli@holomorphy.com,
suresh.b.siddha@intel.com, arjan@infradead.org
Subject: Re: RSDL 0.31 causes slowdown
Date: Fri, 23 Mar 2007 09:57:30 -0800 [thread overview]
Message-ID: <1174672650.23795.67.camel@localhost.localdomain> (raw)
In-Reply-To: <8cd998d50703221940naec0905y56ec708eb11b81a2@mail.gmail.com>
On Fri, 2007-03-23 at 13:40 +1100, Con Kolivas wrote:
>
> Volanomark is a purely yield() semantic dependant workload (as
> discussed many times previously). In the earlier form of RSDL I
> softened the effect of sched_yield but other changes since then have
> made that softness bordering on a noop. Obviously when sched_yield is
> relied upon that will not be enough. Extending the rr interval simply
> makes the yield slightly more effective and is not the proper
> workaround. Since expiration of arrays is a regular frequent
> occurrence in RSDL then changing yield semantics back to expiration
> should cause a massive improvement in these values, without making the
> yields as long as in mainline. It's impossible to know exactly what
> the final result will be since java uses this timing sensitive yield
> for locking but we can improve it drastically from this. I'll make a
> patch soon to change yield again.
>
Con,
The new RSDL 0.33 has fully recovered the loss in performance for
Volanomark. The throughput for Volanomark is at the same level as
mainline 2.6.21-rc4 kernel.
Tim
next prev parent reply other threads:[~2007-03-23 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 21:21 RSDL 0.31 causes slowdown Tim Chen
2007-03-23 2:21 ` William Lee Irwin III
2007-03-23 2:40 ` Con Kolivas
2007-03-23 17:57 ` Tim Chen [this message]
2007-03-26 1:13 ` Con Kolivas
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=1174672650.23795.67.camel@localhost.localdomain \
--to=tim.c.chen@linux.intel.com \
--cc=arjan@infradead.org \
--cc=ck@vds.kolivas.org \
--cc=ckolivas@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=wli@holomorphy.com \
/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