From: Mike Kravetz <mkravetz@sequent.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] Re: multi-queue scheduler update
Date: Fri, 19 Jan 2001 12:32:30 -0800 [thread overview]
Message-ID: <20010119123230.F26968@w-mikek.des.sequent.com> (raw)
In-Reply-To: <20010119091104.A26968@w-mikek.des.sequent.com> <LYR76657-5332-2001.01.19-12.12.38--mikek#sequent.com@lyris.sequent.com>
In-Reply-To: <LYR76657-5332-2001.01.19-12.12.38--mikek#sequent.com@lyris.sequent.com>; from hahn@coffee.psychology.mcmaster.ca on Fri, Jan 19, 2001 at 03:12:11PM -0500
On Fri, Jan 19, 2001 at 03:12:11PM -0500, Mark Hahn wrote:
> > incurred in the current implementation. To maintain existing
> > scheduler behavior, we look at all CPU specific runqueues to find
> > the highest priority (goodness) task in the system. Therefore,
>
> do you have cpu-affinity? the mainstream scheduler at one time
> actually tuned the decision to move a task based on its expected
> timeslice and the worstcase cache-flush time.
We use the same same cpu-affinity mechanism as the current scheduler.
This simply gives a 'priority boost' to tasks that last ran on the
current CPU. In our multi-queue scheduler, tasks on a remote queue
must have high enough priority (to overcome this boost) before being
moved to the local queue.
--
Mike Kravetz mkravetz@sequent.com
IBM Linux Technology Center
15450 SW Koll Parkway
Beaverton, OR 97006-6063 (503)578-3494
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-19 20:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 15:47 Hubertus Franke
2001-01-19 17:11 ` Mike Kravetz
[not found] ` <LYR76657-5332-2001.01.19-12.12.38--mikek#sequent.com@lyris.sequent.com>
2001-01-19 20:32 ` Mike Kravetz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-22 13:35 Hubertus Franke
2001-01-22 16:58 ` Davide Libenzi
2001-01-19 18:03 Hubertus Franke
2001-01-19 19:52 ` bert hubert
2001-01-19 16:47 Hubertus Franke
2001-01-19 16:30 Hubertus Franke
2001-01-19 16:33 ` nick
2001-01-19 17:06 ` Tim Wright
2001-01-18 23:53 Mike Kravetz
2001-01-19 0:26 ` Andrea Arcangeli
2001-01-19 0:51 ` [Lse-tech] " Andi Kleen
2001-01-19 0:52 ` Mike Kravetz
2001-01-19 1:30 ` Andrea Arcangeli
2001-01-19 1:34 ` Mike Kravetz
2001-01-19 20:49 ` Mike Kravetz
2001-01-19 21:51 ` Mike Kravetz
2001-01-19 22:03 ` Davide Libenzi
2001-01-19 22:18 ` Mike Kravetz
2001-01-19 23:24 ` Davide Libenzi
2001-01-19 1:39 ` Davide Libenzi
2001-01-19 16:06 ` David Lang
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=20010119123230.F26968@w-mikek.des.sequent.com \
--to=mkravetz@sequent.com \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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
Powered by JetHome