linux-kernel - Re: Serious performance regression in Wine applications and Linux 2.6.24.*

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]

Message-Id: <1206341640.31427.1243929483@webmail.messagingengine.com>
Date:	Sun, 23 Mar 2008 23:54:00 -0700
From:	"Kai" <epimetreus@...tmail.fm>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Serious performance regression in Wine applications and Linux
   2.6.24.*

On 24 Mar 2008 04:55:36 +0100, "Andi Kleen" <andi@...stfloor.org> said:
> "Kai" <epimetreus@...tmail.fm> writes:
> 
> > Originally, it was just about everything -- Wine itself, and most any
> > app I tried to run with it.
> > 
> > In my most recent tests, however, it only seems to affect Age of Wonders
> > II and Age of Wonders Shadow Magic, which use very similar engines.
> 
> A simple test if the scheduler is likely to blame would be to compare
> context switch rates between the different kernel versions who show
> differing performance. You can do that with running "vmstat 1" in
> parallel and checking the "cs" column.
> 
> Another powerful but quite slow method if you can easily reproduce it
> would be a full git bisect. That would identify exactly which change
> introduced your problem.
> 
> -Andi

Can you explain more clearly what you mean with vmstat?

Also, I'd like to find a way to feasibly do the git bisect (I assume you
basically mean testing against every change in sequence since .23), but
I'd like some advice on how to do this, and how to do it reasonably
expeditiously.
--
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/