From: Con Kolivas <kernel@kolivas.org>
To: "Szonyi Calin" <sony@etc.utt.ro>
Cc: <linux-kernel@vger.kernel.org>, <akpm@osdl.org>
Subject: Re: [PATCH] O3int interactivity for 2.5.74-mm2
Date: Tue, 8 Jul 2003 18:03:23 +1000 [thread overview]
Message-ID: <200307081803.23132.kernel@kolivas.org> (raw)
In-Reply-To: <26071.194.138.39.55.1057648284.squirrel@webmail.etc.utt.ro>
On Tue, 8 Jul 2003 17:11, Szonyi Calin wrote:
> Con Kolivas said:
> > Thanks to Felipe who picked this up I was able to find the one bug
> > causing me grief. The idle detection code was allowing the sleep_avg to
> > get to ridiculously high levels. This is corrected in the following
> > replacement O3int patch. Note this fixes the mozilla issue too. Kick
> > arse!!
> >
> > Con
>
> Not really.
Ok kick my butt instead so I can try and fix it.
> No change on my system.
> No fancy gui (just fvwm). Testing is very simple:
> In one xterm window make bzImage
> in other mplayer /some/movie.avi
> ... and the movie is jerky :-(
Can you tell me how it compares to vanilla at all, and can you watch top and
see what dynamic priorities are reported for the cc and mplayer processes
while it's running?
>
> In the weekend i did some experiments with the defines in kernel/sched.c
> It seems that changing in MAX_TIMESLICE the "200" to "100" or even "50"
> helps a little bit. (i was able to do a make bzImage and watch a movie
> without noticing that is a kernel compile in background)
Strong resistance to dropping the timeslices will remain. If you want to do
this, try adding the granularity patch instead which works better. Neither
will become mainline changes I'm afraid.
>
> system is AMD DURON chipset via KT/KM 133, Ati Radeon VE.
>
> I remeber with nostalgicaly about the times when i could (with a 2.5
> kernel) do a make -j 5 bzImage AND watch a movie in the same time
<sigh> If it were still the case I wouldn't be spending hundreds of hours
doing this :|
Con
next prev parent reply other threads:[~2003-07-08 7:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 17:16 [PATCH] O3int interactivity for 2.5.74-mm2 Con Kolivas
2003-07-06 18:36 ` Felipe Alfaro Solana
2003-07-06 21:14 ` Con Kolivas
2003-07-06 21:17 ` Con Kolivas
2003-07-07 3:19 ` Con Kolivas
2003-07-07 9:13 ` Felipe Alfaro Solana
2003-07-07 9:40 ` Mike Galbraith
2003-07-07 10:25 ` Con Kolivas
2003-07-07 14:06 ` Mike Galbraith
2003-07-07 14:10 ` Con Kolivas
2003-07-07 10:51 ` Nick Sanders
2003-07-07 12:19 ` Marc-Christian Petersen
2003-07-07 13:14 ` Con Kolivas
2003-07-08 0:31 ` Zwane Mwaikambo
2003-07-09 10:12 ` Marc-Christian Petersen
2003-07-09 10:13 ` Marc-Christian Petersen
2003-07-09 10:22 ` Con Kolivas
2003-07-09 10:23 ` Marc-Christian Petersen
2003-07-09 10:37 ` Con Kolivas
2003-07-09 10:40 ` Marc-Christian Petersen
2003-07-07 13:25 ` Helge Hafting
2003-07-08 6:35 ` Alex Riesen
2003-07-08 7:11 ` Szonyi Calin
2003-07-08 7:46 ` Davide Libenzi
2003-07-08 7:59 ` Con Kolivas
2003-07-08 15:12 ` Davide Libenzi
2003-07-08 20:54 ` Con Kolivas
2003-07-08 20:55 ` Davide Libenzi
2003-07-08 8:03 ` Con Kolivas [this message]
2003-07-10 16:27 ` Szonyi Calin
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 15:08 Luis Miguel Garcia
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=200307081803.23132.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sony@etc.utt.ro \
/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