From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: [PATCH]O20.1int
Date: Wed, 10 Sep 2003 13:00:20 +1000 [thread overview]
Message-ID: <200309101300.20634.kernel@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
Should be the last of the O1int patches.
Tiny tweak to keep top two interactive levels round robin at the fastest
(10ms) which keeps X smooth when another interactive task is also using
bursts of cpu (eg web browser).
Credit. Is this too bold?
Con
[-- Attachment #2: patch-O20-O20.1int --]
[-- Type: text/x-diff, Size: 1009 bytes --]
--- linux-2.6.0-test5-mm1-O20/kernel/sched.c 2003-09-10 11:15:45.000000000 +1000
+++ linux-2.6.0-test5-mm1/kernel/sched.c 2003-09-10 11:51:38.000000000 +1000
@@ -14,6 +14,7 @@
* an array-switch method of distributing timeslices
* and per-CPU runqueues. Cleanups and useful suggestions
* by Davide Libenzi, preemptible kernel bits by Robert Love.
+ * 2003-09-03 Interactivity tuning by Con Kolivas.
*/
#include <linux/mm.h>
@@ -122,12 +123,12 @@
MAX_SLEEP_AVG)
#ifdef CONFIG_SMP
-#define TIMESLICE_GRANULARITY(p) \
- (MIN_TIMESLICE * (1 << (MAX_BONUS - CURRENT_BONUS(p))) * \
- num_online_cpus())
+#define TIMESLICE_GRANULARITY(p) (MIN_TIMESLICE * \
+ (1 << (((MAX_BONUS - CURRENT_BONUS(p)) ? : 1) - 1)) * \
+ num_online_cpus())
#else
-#define TIMESLICE_GRANULARITY(p) \
- (MIN_TIMESLICE * (1 << (MAX_BONUS - CURRENT_BONUS(p))))
+#define TIMESLICE_GRANULARITY(p) (MIN_TIMESLICE * \
+ (1 << (((MAX_BONUS - CURRENT_BONUS(p)) ? : 1) - 1)))
#endif
#define SCALE(v1,v1_max,v2_max) \
next reply other threads:[~2003-09-10 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 3:00 Con Kolivas [this message]
2003-09-10 4:31 ` [PATCH]O20.1int Andrew Morton
2003-09-10 16:36 ` [PATCH]O20.1int Cliff White
2003-09-15 12:48 ` [PATCH]O20.1int Måns Rullgård
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=200309101300.20634.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.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