mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Kravetz <kravetz@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch] scheduler cache affinity improvement for 2.4 kernels
Date: Tue, 13 Nov 2001 20:56:13 -0800	[thread overview]
Message-ID: <20011113205613.A1070@w-mikek2.sequent.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111081341400.8863-200000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0111081341400.8863-200000@localhost.localdomain>; from mingo@elte.hu on Thu, Nov 08, 2001 at 03:30:11PM +0100

On Thu, Nov 08, 2001 at 03:30:11PM +0100, Ingo Molnar wrote:
> 
> i've attached a patch that fixes a long-time performance problem in the
> Linux scheduler.

Just got back from holiday and saw this patch.  I like the idea
slowing down task dynamic priority modifications (the counter
field).  My only thought/concern would be in the case where a
task with maximum dynamic priority (counter value) decides to
use 'all' of its timeslice.  In such a case, the task can not
be preempted by another task (with the same static priority)
until its entire timeslice is expired.  In the current scheduler,
I believe the task can be preempted after 1 timer tick.  In
practice, this shouldn't be an issue.  However, it is something
we may want to think about.  One simple solution would be to
update a tasks dynamic priority (counter value) more frequently
it it is above its NICE_TO_TICKS value.

> (it would be nice if those people who suspect scalability problems in
> their workloads, could further test/verify the effects this patch.)

I'll try to run it on my 'CPU intensive' version of the TPC-H
behcnmark.

In addition, I have noted that this patch applies with minor
modification to our MultiQueue scheduler, and should be a win
in this environment also.

-- 
Mike

  parent reply	other threads:[~2001-11-14  4:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 14:30 Ingo Molnar
2001-11-08 15:22 ` M. Edward Borasky
2001-11-08 16:33   ` Ingo Molnar
2001-11-08 17:15 ` Davide Libenzi
2001-11-08 18:27   ` Ingo Molnar
2001-11-08 18:03     ` Davide Libenzi
2001-11-08 19:40       ` Ingo Molnar
2001-11-08 19:13         ` Davide Libenzi
2001-11-08 23:37           ` Mike Fedyk
2001-11-09  0:37             ` Davide Libenzi
2001-11-09  1:07               ` Mike Fedyk
2001-11-09  1:29                 ` Davide Libenzi
2001-11-09  1:34                   ` Mike Fedyk
2001-11-09  2:09                     ` Davide Libenzi
2001-11-09  2:08                       ` Mike Fedyk
2001-11-19 18:34               ` bill davidsen
2001-11-09  8:28             ` Ingo Molnar
2001-11-09  8:05               ` Mike Fedyk
2001-11-11 21:18               ` Davide Libenzi
2001-11-11 22:31                 ` Davide Libenzi
2001-11-08 23:46 ` Andrea Arcangeli
2001-11-09  0:31 ` Davide Libenzi
2001-11-14  4:56 ` Mike Kravetz [this message]
2001-11-14 18:08   ` Davide Libenzi

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=20011113205613.A1070@w-mikek2.sequent.com \
    --to=kravetz@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®