From: Martin Roehricht <ml@felicis.org>
To: linux-kernel@vger.kernel.org
Subject: highest and lowest priority job of a runqueue
Date: Wed, 25 Jul 2007 11:48:28 +0200 [thread overview]
Message-ID: <46A71C6C.2050207@felicis.org> (raw)
Hi,
I have some questions concerning the current 2.6.22 scheduler
implementation. I was wondering how I may retrieve
(a) the priority/load of the highest and the lowest priority task of a
runqueue (in a multiprocessor system), and
(b) the corresponding pointer to this task?
I thought I might use (given a list with tmp pointers to all CPUs)
rq = cpu_rq(tmp->cpu);
task_load = rq->curr->load_weight;
but this always returns 128 regardless of the fact if a task currently
runs on that CPU or not. I guess it returns the load of the migration
thread, but I'm not sure. I would like to migrate specific tasks
throughout find_busiest_group().
Furthermore, is it correct, that the current migration strategy
(move_tasks()) chooses automatically the highest priority task?
Thanks for your help,
Martin
next reply other threads:[~2007-07-25 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 9:48 Martin Roehricht [this message]
[not found] <8KLFD-G9-5@gated-at.bofh.it>
2007-07-25 15:18 ` highest and lowest priority job of a runqueue 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=46A71C6C.2050207@felicis.org \
--to=ml@felicis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.