From: Martin Roehricht <ml@felicis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling the highest priority task
Date: Thu, 02 Aug 2007 17:00:18 +0200 [thread overview]
Message-ID: <46B1F182.3010608@felicis.org> (raw)
In-Reply-To: <20070802114012.GA4067@elte.hu>
On 08/02/2007 01:40 PM, Ingo Molnar wrote:
> in the SMP migration code, the 'old scheduler' indeed picks the lowest
> priority one, _except_ if that task is running on another CPU or is too
> 'cache hot':
But why is it, that the scheduler picks the lowest priority one? I
thought sched_find_first_bit() picks the index of the lowest order bit
in the bitmap and thus the highest priority job. Is that wrong?
What needs to be changed to let the scheduler pick the highest priority
task from a given runqueue?
I am very confused ...
Martin
next prev parent reply other threads:[~2007-08-02 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8KLFD-G9-5@gated-at.bofh.it>
2007-07-25 15:18 ` highest and lowest priority job of a runqueue Martin Roehricht
2007-08-02 8:58 ` Scheduling the highest priority task Martin Roehricht
2007-08-02 11:40 ` Ingo Molnar
2007-08-02 15:00 ` Martin Roehricht [this message]
2007-08-02 15:03 ` Ingo Molnar
2007-08-02 15:14 ` Martin Roehricht
2007-08-02 15:19 ` Ingo Molnar
2007-08-02 15:46 ` Martin Roehricht
2007-08-02 19:48 ` Ingo Molnar
2007-08-02 21:05 ` Martin Roehricht
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=46B1F182.3010608@felicis.org \
--to=ml@felicis.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