From: Andi Kleen <andi@firstfloor.org>
To: Kai <epimetreus@fastmail.fm>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Serious performance regression in Wine applications and Linux 2.6.24.*
Date: Mon, 24 Mar 2008 08:09:15 +0100 [thread overview]
Message-ID: <20080324070915.GA15022@one.firstfloor.org> (raw)
In-Reply-To: <1206341640.31427.1243929483@webmail.messagingengine.com>
> Can you explain more clearly what you mean with vmstat?
Open shell window. Enter "vmstat 1". Run Wine application. Watch "cs"
column over time.
An possible improvement would be also to use a larger number than 1 to get
values over long time.
Compare that value to the old kernel.
>
> 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
Yes, although it is just every 1+log2 changes
> I'd like some advice on how to do this, and how to do it reasonably
> expeditiously.
Type git bisect into google, there are lots of tutorials.
-Andi
>
next prev parent reply other threads:[~2008-03-24 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 22:10 Serious performance regression in Wine applications and Linux 2.6.24.* Kai
2008-03-23 22:22 ` Ray Lee
2008-03-24 6:57 ` Kai
2008-03-27 9:17 ` Ingo Molnar
2008-04-03 14:04 ` Kai
[not found] ` <1207250856.9779.1245934881@webmail.messagingengine.com>
2008-04-21 15:53 ` Ingo Molnar
2008-04-22 2:58 ` Kai
2008-08-07 15:05 ` Kai
2008-03-24 3:55 ` Andi Kleen
2008-03-24 6:54 ` Kai
2008-03-24 7:09 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-23 2:49 Kai
2008-03-23 4:47 ` Ray Lee
2008-03-23 10:03 ` Kai
2008-03-25 12:12 ` Kai
2008-03-25 15:49 ` Ray Lee
[not found] ` <1207139425.16127.1245640599@webmail.messagingengine.com>
2008-04-02 12:40 ` Kai
2008-03-23 10:44 ` David
[not found] ` <1206309824.16550.1243881033@webmail.messagingengine.com>
2008-03-23 22:59 ` David
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=20080324070915.GA15022@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=epimetreus@fastmail.fm \
--cc=linux-kernel@vger.kernel.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