linux-kernel - Re: RSDL 0.31 causes slowdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Mar 2007 09:57:30 -0800
From:	Tim Chen <tim.c.chen@...ux.intel.com>
To:	Con Kolivas <ckolivas@...il.com>
Cc:	ck@....kolivas.org, linux-kernel@...r.kernel.org,
	kernel@...ivas.org, wli@...omorphy.com, suresh.b.siddha@...el.com,
	arjan@...radead.org
Subject: Re: RSDL 0.31 causes slowdown

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/