From: Con Kolivas <kernel@kolivas.org>
To: Timothy Miller <miller@techsource.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]O14int
Date: Sat, 9 Aug 2003 10:44:16 +1000 [thread overview]
Message-ID: <200308091044.16296.kernel@kolivas.org> (raw)
In-Reply-To: <3F33E46D.9040508@techsource.com>
On Sat, 9 Aug 2003 03:57, Timothy Miller wrote:
> Con Kolivas wrote:
> > Made highly interactive tasks earn all their waiting time on the runqueue
> > during requeuing as sleep_avg.
>
> There are some mechanics of this that I am not familiar with, so please
> excuse the naive question.
>
> Someone had suggested that a task's sleep time should be determine
> exclusively from the time it spends blocked by what it's waiting on, and
> not based on any OTHER time it sleeps. That is, the time between the
> I/O request being satisfied and the task actually getting the CPU
> doesn't count.
>
> Is your statement above a reflection of that suggestion?
I have already been doing this in previous iterations to the extent that it
was capable of being done. There's only so much information feeding into the
scheduler at the moment. All the dependent subsections would have to have
more code to have specific feedback to the scheduler.
Con
next prev parent reply other threads:[~2003-08-09 0:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 15:49 [PATCH]O14int Con Kolivas
2003-08-08 17:57 ` [PATCH]O14int Timothy Miller
2003-08-09 0:44 ` Con Kolivas [this message]
2003-08-08 19:31 ` [PATCH]O14int Felipe Alfaro Solana
2003-08-09 9:04 ` [PATCH]O14int Con Kolivas
2003-08-11 5:44 ` [PATCH]O14int Martin Schlemmer
2003-08-11 6:08 ` [PATCH]O14int Con Kolivas
2003-08-11 8:35 ` [PATCH]O14int Martin Schlemmer
2003-08-11 8:37 ` [PATCH]O14int Zwane Mwaikambo
2003-08-11 9:07 ` [PATCH]O14int Con Kolivas
2003-08-11 9:15 ` [PATCH]O14int Nick Piggin
2003-08-11 9:43 ` [PATCH]O14int Con Kolivas
2003-08-11 9:44 ` [PATCH]O14int Nick Piggin
2003-08-11 14:04 ` [PATCH]O14int Martin Schlemmer
2003-08-11 14:33 ` [PATCH]O14int Con Kolivas
2003-08-11 15:19 ` [PATCH]O14int Martin Schlemmer
2003-08-13 6:48 ` [PATCH]O14int Con Kolivas
2003-08-14 6:19 ` [PATCH]O14int William Lee Irwin III
2003-08-15 23:40 ` [PATCH]O14int Paul Dickson
2003-08-17 2:20 ` [PATCH]O14int William Lee Irwin III
2003-08-11 16:31 ` [PATCH]O14int Mike Galbraith
2003-08-11 23:54 ` [PATCH]O14int Timothy Miller
2003-08-11 13:58 ` [PATCH]O14int Martin Schlemmer
2003-08-11 17:55 ` [PATCH]O14int William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 20:08 [PATCH]O14int Voluspa
2003-08-09 0:36 ` [PATCH]O14int Con Kolivas
2003-08-10 8:48 ` [PATCH]O14int Simon Kirby
2003-08-10 9:06 ` [PATCH]O14int Con Kolivas
2003-08-12 17:56 ` [PATCH]O14int Simon Kirby
2003-08-12 21:21 ` [PATCH]O14int Con Kolivas
2003-08-10 10:08 ` [PATCH]O14int William Lee Irwin III
2003-08-12 18:36 ` [PATCH]O14int Simon Kirby
2003-08-10 11:17 ` [PATCH]O14int Mike Galbraith
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=200308091044.16296.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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