From: "Ray Lee" <ray-lk@madrabbit.org>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Poor performance now? Please, put weighted velocities ctxts/s to the sched.decision!
Date: Tue, 25 Mar 2008 13:38:44 -0700 [thread overview]
Message-ID: <2c0942db0803251338n47dba8e5l1364b30adbf415be@mail.gmail.com> (raw)
In-Reply-To: <998d0e4a0803251329o4dabd28ck5197838fe6920441@mail.gmail.com>
On Tue, Mar 25, 2008 at 1:29 PM, J.C. Pizarro <jcpiza@gmail.com> wrote:
> [2] "Re: Serious performance regression in Wine applications and Linux 2.6.24.*"
> http://lkml.org/lkml/2008/3/25/181
> On Tue, 25 Mar 2008 08:49:13 -0700, "Ray Lee" wrote:
> > Andi's idea of looking for excessive context switches is good -- I
> > didn't see a response to that one. Other than that, if you're only
> > noticing the issue in 3d games, then it could be several things (not
> > just the scheduler).
>
> The kernel needed the velocity parameter to gain it: ctxts per interval
> (normally ctxts/s or ctxts/minute).
We don't know that's the problem yet. The reporter is doing more testing.
> "Please, put 64-bit counter per task and incr.by.one each ctxt switch."
> http://lkml.org/lkml/2008/2/23/398
> http://lkml.org/lkml/2008/2/23/401
> http://lkml.org/lkml/2008/2/23/406
> http://lkml.org/lkml/2008/2/24/1
> http://lkml.org/lkml/2008/2/24/103
> http://lkml.org/lkml/2008/2/24/157
> http://lkml.org/lkml/2008/2/26/159
There are already counters recording the switches:
http://lkml.org/lkml/2008/2/25/314
> My proposal is free for yours, quasi-bastards, I won't charge you!
My parents were married.
next prev parent reply other threads:[~2008-03-25 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 20:29 J.C. Pizarro
2008-03-25 20:38 ` Ray Lee [this message]
2008-03-25 20:50 ` J.C. Pizarro
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=2c0942db0803251338n47dba8e5l1364b30adbf415be@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=jcpiza@gmail.com \
--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
all inboxes | Powered by JetHome®