From: Ingo Molnar <mingo@elte.hu>
To: Martin Roehricht <ml@felicis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling the highest priority task
Date: Thu, 2 Aug 2007 17:19:16 +0200 [thread overview]
Message-ID: <20070802151916.GA8688@elte.hu> (raw)
In-Reply-To: <46B1F4BA.4010107@felicis.org>
* Martin Roehricht <ml@felicis.org> wrote:
> That's fine with me, that within the same priority-queue any task can
> be chosen. But assume two tasks with highly different priorities, such
> as 105 and 135 are scheduled on the same processor and one of them is
> now to be migrated -- shouldn't be the queue with task P=105
> considered first for migration by this code? Both tasks would use
> different queues with their own linked lists, right?
yes. What makes you believe that the lower priority one (prio 135) is
chosen? [ as i said before, that will only be chosen if all tasks in the
higher-priority queue (prio 105) are either already running on a CPU or
have recently run so that the cache-hot logic skips them. ]
Ingo
next prev parent reply other threads:[~2007-08-02 15:19 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
2007-08-02 15:03 ` Ingo Molnar
2007-08-02 15:14 ` Martin Roehricht
2007-08-02 15:19 ` Ingo Molnar [this message]
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=20070802151916.GA8688@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@felicis.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