public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] add requeue task
Date: Tue, 02 Nov 2004 23:52:40 +1100	[thread overview]
Message-ID: <41878318.8020801@kolivas.org> (raw)
In-Reply-To: <20041102124252.GE15290@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

Ingo Molnar wrote:
> * Con Kolivas <kernel@kolivas.org> wrote:
> 
> 
>>add requeue task
> 
> 
> ack for this bit, but please split this one out:
> 
> | Change the granularity code to requeue tasks at their best priority
> | instead of changing priority while they're running. This keeps tasks 
> | at their top interactive level during their whole timeslice.
> 
> this is a behavioral change and should go into the 'possible negative
> effect on interactivity' bucket. (of course it could very likely have a
> positive effect as well - the bucket is just to separate the risks.)

Actually I'd like to say I did it for positive effect to counter the 
change that occurred with dropping interactive credit. That was what I 
found in my testing, and I'd like them both to go together into -mm.

Con

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-11-02 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  4:07 [PATCH] add requeue task Con Kolivas
2004-11-02 12:35 ` Nick Piggin
2004-11-02 15:16   ` Nikita Danilov
2004-11-02 22:07     ` Nick Piggin
2004-11-03  8:12     ` Con Kolivas
2004-11-02 12:42 ` Ingo Molnar
2004-11-02 12:52   ` Con Kolivas [this message]
2004-11-02 12:58     ` Ingo Molnar
2004-11-02 14:02       ` [PATCH] requeue at granularity intervals Con Kolivas
2004-11-02 14:00   ` [PATCH] add requeue task redo 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=41878318.8020801@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.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