From: Con Kolivas <kernel@kolivas.org>
To: Charlie Baylis <cb-lkml@fish.zetnet.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O12.2int for interactivity
Date: Tue, 5 Aug 2003 12:10:42 +1000 [thread overview]
Message-ID: <200308051210.42779.kernel@kolivas.org> (raw)
In-Reply-To: <20030804195058.GA8267@cray.fish.zetnet.co.uk>
On Tue, 5 Aug 2003 05:50, Charlie Baylis wrote:
> > I tried them aggressively; irman2 and thud don't hurt here. The idle
> > detection limits both of them from gaining too much sleep_avg while
> > waiting around and they dont get better dynamic priority than 17.
>
> Sounds like you've taken the teeth out of the thud program :) The original
> aim was to demonstrate what happens when a maximally interactive task
> suddenly becomes a CPU hog - similar to a web browser starting to render
> and causing intense X activity in the process. Stopping thud getting
> maximum priority is addressing the symptom, not the cause. (That's not to
> say the idle detection is a bad idea - but it's not the complete answer)
It was a side effect that it helped this particular issue. The idle detection
was based around helping real world scenarios and it just happened to help.
> the idea is to do a little bit of work so that the idle detection doesn't
> kick in and thud can reach the max interactive bonus. (I haven't tried your
> patch yet to see if this change achieves this)
Good call; I was quite aware this is the most effective way to create a fork
bomb with my patch, but it's effect while being noticably worse than the
original thud is still not disastrous. Yes I do appreciate variations on the
theme can be made worse again; I'm doing some testing and experimenting there
to see how best to tackle it.
Con
next prev parent reply other threads:[~2003-08-05 2:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 19:50 [PATCH] O12.2int for interactivity Charlie Baylis
2003-08-05 2:10 ` Con Kolivas [this message]
2003-08-05 22:49 ` Timothy Miller
2003-08-06 0:12 ` charlie.baylis
2003-08-06 1:23 ` Con Kolivas
2003-08-06 22:24 ` Timothy Miller
2003-08-11 8:14 ` Rob Landley
2003-08-11 23:49 ` Timothy Miller
2003-08-12 0:17 ` William Lee Irwin III
2003-08-12 15:04 ` Timothy Miller
2003-08-12 23:32 ` William Lee Irwin III
2003-08-13 15:46 ` Timothy Miller
2003-08-14 6:09 ` William Lee Irwin III
2003-08-14 6:59 ` Con Kolivas
2003-08-14 7:01 ` William Lee Irwin III
2003-08-14 7:46 ` Con Kolivas
2003-08-14 20:03 ` Timothy Miller
2003-08-15 16:40 ` Con Kolivas
2003-08-14 20:00 ` Timothy Miller
2003-08-15 16:38 ` Con Kolivas
2003-08-15 18:12 ` Timothy Miller
2003-08-17 2:19 ` William Lee Irwin III
2003-08-17 18:00 ` Mike Fedyk
2003-08-14 19:57 ` Timothy Miller
2003-08-15 16:35 ` Con Kolivas
2003-08-15 18:17 ` Timothy Miller
2003-08-16 2:29 ` Con Kolivas
2003-08-14 19:54 ` Timothy Miller
-- strict thread matches above, loose matches on Subject: below --
2003-08-03 21:19 Voluspa
2003-08-04 2:34 ` Con Kolivas
2003-08-03 10:14 Con Kolivas
2003-08-03 11:25 ` Ingo Molnar
2003-08-03 11:36 ` Con Kolivas
2003-08-04 3:06 ` Con Kolivas
2003-08-03 11:37 ` Felipe Alfaro Solana
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=200308051210.42779.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=cb-lkml@fish.zetnet.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).