From: Daniel Phillips <phillips@arcor.de>
To: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH] O1int 0307021808 for interactivity
Date: Thu, 3 Jul 2003 18:29:29 +0200 [thread overview]
Message-ID: <200307031829.29219.phillips@arcor.de> (raw)
In-Reply-To: <200307040034.49102.kernel@kolivas.org>
On Thursday 03 July 2003 16:34, Con Kolivas wrote:
> On Fri, 4 Jul 2003 00:27, Daniel Phillips wrote:
> > I'm still pretty much in the dark after that. It says something about
> > your patch, but it doesn't say much about the problem you're solving,
> > i.e., what's the Context? (pun intended)
>
> Basically? Who gets to preempt who and for how long. The interactivity
> estimator should decide that the correct task is interactive and get a
> dynamically higher priority and larger timeslice. Is this what you're
> asking?
I guess what I'm saying is, the problem is far from solved, however your
concrete results demonstrate you've got an intuitive grasp of how to go at
it. I'd like to dig in and find out what the deep issues are. As I've
basically ignored scheduling up to now, including all of the details of
Ingo's work, there's some background to fill in. Being lazy, I'd prefer to
read somebody's detailed [rfc] instead of going through the process of
reverse engineering it myself. I presume I'm not the only one.
Regards,
Daniel
next prev parent reply other threads:[~2003-07-03 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 8:23 [PATCH] O1int 0307021808 for interactivity Con Kolivas
2003-07-03 11:46 ` Daniel Phillips
2003-07-03 12:21 ` Con Kolivas
2003-07-03 14:27 ` Daniel Phillips
2003-07-03 14:34 ` Con Kolivas
2003-07-03 16:29 ` Daniel Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 9:17 Luis Miguel Garcia
2003-07-02 9:53 ` Con Kolivas
2003-07-02 10:09 ` Luis Miguel Garcia
2003-07-02 10:12 ` Luis Miguel Garcia
2003-07-02 10:10 ` Con Kolivas
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=200307031829.29219.phillips@arcor.de \
--to=phillips@arcor.de \
--cc=akpm@digeo.com \
--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