From: Mike Galbraith <efault@gmx.de>
To: Michal Schmidt <schmidt@kn.vutbr.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reproducible terrible interactivity since 2.5.64bk2
Date: Mon, 31 Mar 2003 04:26:55 +0200 [thread overview]
Message-ID: <5.2.0.9.2.20030331042453.00cee3a8@pop.gmx.net> (raw)
In-Reply-To: <3E8774FA.7070209@kn.vutbr.cz>
At 12:51 AM 3/31/2003 +0200, Michal Schmidt wrote:
>Mike Galbraith wrote:
>>Greetings potential victims :)
>>Care to see if the attached cures your woes?
>>This is a mixture of Ingo's last posted plus the scheduler tuning knobs
>>patch (/proc/sys/sched/*). I added three new knobs to watch the effect
>>on different loads. max_accel_slices limits the amount of sleep_time you
>>may add in one activation. retard_prct_slices is a percentage of a slice
>>to deduct from sleep_time each activation (negative feedback for heavy
>>context switchers.. dang irman process_load). force_switch is there
>>because I'm playing :) I didn't do much to the scheduler itself, only
>>made it switch arrays in something closer to a square wave. With the
>>settings as in the patch, and running a kernel build, top and irman,
>>irman reports worst case response times of 150ms for NULL load, 316ms for
>>memory_load, 414 for io_load, and 504ms for process_load.
>>Anyway, it's attached if you want to play with it ;-)
>> -Mike
>>Oh, it's against virgin 2.5.66.
>
>
>Thanks, running 2.5.66 with the patch applied I could no more reproduce
>the problem. I haven't tried playing with the knobs.
Thanks for the info.
-Mike
next prev parent reply other threads:[~2003-03-31 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 11:51 Michal Schmidt
2003-03-26 14:08 ` Andrew Ebling
2003-03-26 14:16 ` Michal Schmidt
2003-03-26 14:40 ` Andrew Ebling
2003-03-28 17:50 ` Mike Galbraith
2003-03-28 19:54 ` Mike Galbraith
2003-03-30 22:51 ` Michal Schmidt
2003-03-31 2:26 ` Mike Galbraith [this message]
2003-03-26 18:25 ` Felipe Alfaro Solana
2003-03-26 18:41 ` Bill Davidsen
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=5.2.0.9.2.20030331042453.00cee3a8@pop.gmx.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schmidt@kn.vutbr.cz \
/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®