From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <piggin@cyberone.com.au>, Andrew Morton <akpm@osdl.org>
Cc: Johoho <johoho@hojo-net.de>,
wodecki@gmx.de, Valdis.Kletnieks@vt.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O10int for interactivity
Date: Thu, 31 Jul 2003 17:43:17 +1000 [thread overview]
Message-ID: <200307311743.17370.kernel@kolivas.org> (raw)
In-Reply-To: <3F28B8D5.4040600@cyberone.com.au>
On Thu, 31 Jul 2003 16:36, Nick Piggin wrote:
> Oh, and the process scheduler can definitely be a contributing factor.
> Even if it looks like your process is getting enough cpu, if your
> process doesn't get woken in less than 5ms after its read completes,
> then AS will give up waiting for it.
This part interests me. It would seem that either
1. The AS scheduler should not bother waiting at all if the process is not
going to wake up in that time
2. The process should be woken in that time to ensure the AS scheduler is not
wasting it's time waiting.
or a combination of 1 and 2 depending on some heuristic deciding on how
important it is for 2 instead of 1.
No, I'm not planning on trying to implement either of these <insert usual
complaint about time and knowledge here>, but I thought I should at least
contribute my thoughts.
Con
next prev parent reply other threads:[~2003-07-31 7:38 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
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 [this message]
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
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=200307311743.17370.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=johoho@hojo-net.de \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=wodecki@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).