From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Andrew Morton <akpm@osdl.org>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH] sched: Avoid unnecessarily moving highest priority task move_tasks()
Date: Mon, 24 Apr 2006 16:48:00 -0700 [thread overview]
Message-ID: <20060424164800.B16716@unix-os.sc.intel.com> (raw)
In-Reply-To: <444D5989.3060002@bigpond.net.au>; from pwil3058@bigpond.net.au on Tue, Apr 25, 2006 at 09:04:41AM +1000
On Tue, Apr 25, 2006 at 09:04:41AM +1000, Peter Williams wrote:
> Looks like there's a NOT missing doesn't it. So there is an error but I
> don't think that your patch is the right way to fix it. We just need to
> negate the above assignment. E.g.
>
> skip_for_load = !(busiest_best_prio_seen || idx != busiest_best_prio);
>
> or
>
> skip_for_load = !busiest_best_prio_seen && idx == busiest_best_prio;
>
> whichever is more efficient.
That just will not be enough. busiest_best_prio needs to be set to '1'
whenever we skip the first best priority task(not whenever we move it)
And we also need to initialize busiest_best_prio_seen inside this check.
(like in my patch)
if (busiest->expired->nr_active) {
And we need to reset busiest_best_prio_seen to '0' whenever we finished
the checking of expired list (and move onto active list) and there are
no best prio tasks on expired list..
> > @@ -2072,6 +2067,13 @@ static int move_tasks(runqueue_t *this_r
> > if (busiest->expired->nr_active) {
> > array = busiest->expired;
> > dst_array = this_rq->expired;
> > + /*
> > + * We already have one or more busiest best prio tasks on
> > + * active list.
>
> This is a pretty bold assertion. How do we know that this is true.
That comment refers to when 'busiest_best_prio_seen' is initialized to '1'.
Comment needs to be fixed.
thanks,
suresh
>
> > So if we encounter any busiest best prio task
> > + * on expired list, consider it for the move, if it becomes
> > + * the best prio on new queue.
> > + */
> > + busiest_best_prio_seen = busiest_best_prio == busiest->curr->prio;
> > } else {
> > array = busiest->active;
> > dst_array = this_rq->active;
> > @@ -2089,6 +2091,7 @@ skip_bitmap:
> > if (array == busiest->expired && busiest->active->nr_active) {
> > array = busiest->active;
> > dst_array = this_rq->active;
> > + busiest_best_prio_seen = 0;
> > goto new_array;
> > }
> > goto out;
> > @@ -2107,8 +2110,9 @@ skip_queue:
> > * prio value) on its new queue regardless of its load weight
> > */
> > skip_for_load = tmp->load_weight > rem_load_move;
> > - if (skip_for_load && idx < this_best_prio)
> > - skip_for_load = busiest_best_prio_seen || idx != busiest_best_prio;
> > + if (skip_for_load && idx < this_best_prio && idx == busiest_best_prio)
> > + skip_for_load = !busiest_best_prio_seen &&
> > + head->next == head->prev;
> > if (skip_for_load ||
> > !can_migrate_task(tmp, busiest, this_cpu, sd, idle, &pinned)) {
> > if (curr != head)
> > @@ -2133,8 +2137,6 @@ skip_queue:
> > if (pulled < max_nr_move && rem_load_move > 0) {
> > if (idx < this_best_prio)
> > this_best_prio = idx;
> > - if (idx == busiest_best_prio)
> > - busiest_best_prio_seen = 1;
> > if (curr != head)
> > goto skip_queue;
> > idx++;
>
>
> Peter
> --
> Peter Williams pwil3058@bigpond.net.au
>
> "Learning, n. The kind of ignorance distinguishing the studious."
> -- Ambrose Bierce
next prev parent reply other threads:[~2006-04-24 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 4:22 [PATCH] sched: Avoid unnecessarily moving highest priority task move_tasks() Peter Williams
2006-04-22 0:34 ` Siddha, Suresh B
2006-04-22 1:31 ` Peter Williams
2006-04-24 19:00 ` Siddha, Suresh B
2006-04-24 23:04 ` Peter Williams
2006-04-24 23:48 ` Siddha, Suresh B [this message]
2006-04-25 2:30 ` Peter Williams
2006-04-25 21:32 ` Siddha, Suresh B
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=20060424164800.B16716@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kenneth.w.chen@intel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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