From: Wiktor Wodecki <wodecki@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O10int for interactivity
Date: Mon, 28 Jul 2003 09:51:06 +0200 [thread overview]
Message-ID: <20030728075106.GA660@gmx.de> (raw)
In-Reply-To: <200307280112.16043.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
On Mon, Jul 28, 2003 at 01:12:16AM +1000, Con Kolivas wrote:
> Here is a fairly rapid evolution of the O*int patches for interactivity thanks
> to Ingo's involvement.
>
> Changes:
> I've put in some defines to clarify where the numbers for MAX_SLEEP_AVG come
> from now, rather than the number being magic. In the process it increases MSA
> every so slightly so that an average task that runs a full timeslice (102ms)
> will drop exactly one priority in that time.
>
> I've incorporated Ingo's fix for scheduling latency in a form that works for
> my patch, along with the other minor tweaks.
>
> The parent and child sleep avg on forking is set to just on the priority bonus
> value with each fork thus keeping their bonus the same but making them very
> easy to tip to a lower priority.
>
> A tiny addition to ensure any task that runs gets charged one tick of
> sleep_avg.
>
> This patch is against 2.6.0-test1-mm2 patched up to O9int. An updated
> O9int with layout corrections was posted on my website. A full O10int patch
> against 2.6.0-test1 is available on my website.
okay, applied O10 on top of 2.6.0-test2. The same problem I wrote you
yesterday about O9, when starting OpenOffice and bzip2'ing in the
background OO becomes nearly unusable - I can type a sentence and watch
the characters appear. I don't know if this was always the case since I
haven't used OO before that much (need it for the university now)
--
Regards,
Wiktor Wodecki
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-28 7:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 15:12 [PATCH] O10int for interactivity Con Kolivas
2003-07-27 16:26 ` Wade
2003-07-27 19:15 ` Felipe Alfaro Solana
2003-07-28 7:51 ` Wiktor Wodecki [this message]
2003-07-28 7:55 ` Andrew Morton
2003-07-28 8:00 ` Wiktor Wodecki
2003-07-28 17:12 ` Jose Luis Domingo Lopez
2003-07-28 18:08 ` Valdis.Kletnieks
2003-07-28 18:40 ` Andrew Morton
2003-07-28 21:29 ` Wiktor Wodecki
2003-07-28 21:35 ` Andrew Morton
2003-07-31 6:36 ` Nick Piggin
2003-07-31 7:43 ` Con Kolivas
2003-07-31 7:58 ` Nick Piggin
2003-07-31 14:59 ` Jamie Lokier
2003-07-31 15:24 ` Oliver Neukum
2003-07-31 15:40 ` Jamie Lokier
2003-07-31 22:56 ` Nick Piggin
2003-08-04 18:51 ` [PATCH] O13int " Felipe Alfaro Solana
2003-08-04 18:58 ` Felipe Alfaro Solana
2003-08-04 21:46 ` Con Kolivas
2003-08-04 22:16 ` Felipe Alfaro Solana
2003-07-29 14:21 ` [PATCH] O10int " Timothy Miller
2003-07-29 14:35 ` Con Kolivas
2003-07-29 15:35 ` Timothy Miller
2003-07-30 1:16 ` Diego Calleja García
2003-07-30 1:36 ` Con Kolivas
2003-07-30 19:28 ` aradorlinux
2003-07-30 19:34 ` Andrew Morton
2003-07-29 15:28 ` Valdis.Kletnieks
2003-07-29 15:44 ` Timothy Miller
2003-07-29 15:45 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2003-07-27 19:50 Voluspa
2003-07-28 2:05 Voluspa
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=20030728075106.GA660@gmx.de \
--to=wodecki@gmx.de \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--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