From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] sched-2.6.0-test1-G6, interactivity changes
Date: Mon, 28 Jul 2003 00:03:04 +1000 [thread overview]
Message-ID: <200307280003.05185.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0307271535590.22937-100000@localhost.localdomain>
On Sun, 27 Jul 2003 23:40, Ingo Molnar wrote:
> - further increase timeslice granularity
For a while now I've been running a 1000Hz 2.4 O(1) kernel tree that uses
timeslice granularity set to MIN_TIMESLICE which has stark smoothness
improvements in X. I've avoided promoting this idea because of the
theoretical drop in throughput this might cause. I've not been able to see
any detriment in my basic testing of this small granularity, so I was curious
to see what you throught was a reasonable lower limit?
Con
next prev parent reply other threads:[~2003-07-27 13:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 13:40 [patch] sched-2.6.0-test1-G6, interactivity changes Ingo Molnar
2003-07-27 14:03 ` Con Kolivas [this message]
2003-07-28 7:24 ` Ingo Molnar
2003-07-28 8:50 ` Con Kolivas
2003-07-28 21:38 ` Bill Davidsen
2003-07-28 22:00 ` Con Kolivas
2003-07-30 2:49 ` Bill Davidsen
2003-08-08 19:41 ` Rob Landley
2003-07-27 19:18 ` Felipe Alfaro Solana
2003-07-28 6:04 ` Mike Galbraith
2003-07-28 6:45 ` Andre Hedrick
2003-07-28 7:05 ` Con Kolivas
2003-07-28 7:33 ` Mike Galbraith
2003-07-28 7:44 ` Ingo Molnar
2003-07-30 14:24 ` Szonyi Calin
[not found] ` <Pine.LNX.4.44.0307280935300.4596-100000@localhost.localdom ain>
2003-07-28 8:15 ` Mike Galbraith
2003-07-28 8:42 ` Con Kolivas
2003-07-28 8:49 ` Mike Galbraith
[not found] ` <Pine.LNX.4.10.10307272338160.30891-100000@master.linux-ide .org>
2003-07-28 7:27 ` Mike Galbraith
2003-07-28 17:33 ` Andre Hedrick
[not found] ` <Pine.LNX.4.10.10307281030180.30891-100000@master.linux-ide .org>
2003-07-29 7:44 ` Mike Galbraith
2003-07-28 17:17 ` Jose Luis Domingo Lopez
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=200307280003.05185.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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