From: Steven Rostedt <rostedt@goodmis.org>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [sched/rt] Optimization of function pull_rt_task()
Date: Wed, 18 Apr 2012 14:32:56 -0400 [thread overview]
Message-ID: <1334773976.28106.49.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1334592379.28106.4.camel@gandalf.stny.rr.com>
On Mon, 2012-04-16 at 12:06 -0400, Steven Rostedt wrote:
> On Sun, 2012-04-15 at 23:45 +0400, Kirill Tkhai wrote:
> > The condition (src_rq->rt.rt_nr_running) is weak because it doesn't
> > consider the cases when src_rq has only processes bound to it (when
> > single cpu is allowed). It may be running kernel thread like
> > migration/x etc.
> >
> > So it's better to use more stronger condition which is able to exclude
> > above conditions. The function has_pushable_tasks() complitely does
> > this. A task may be pullable for another cpu rq only if he is pushable
> > for his own queue.
>
> I considered this before, and for some reason I never did the change.
> I'll have to think about it. It seems like this would be the obvious
> case, but I think there was something not so obvious that caused issues.
> But I don't remember what it was.
>
> I'll have to rethink this again.
I can't find anything wrong with this change. Maybe things change, or I
was thinking of another change.
I'll apply it and start running my tests against it.
Thanks!
-- Steve
next prev parent reply other threads:[~2012-04-18 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 19:45 Kirill Tkhai
2012-04-16 16:06 ` Steven Rostedt
2012-04-18 18:32 ` Steven Rostedt [this message]
2012-04-18 21:16 ` Steven Rostedt
2012-04-19 8:54 ` Yong Zhang
2012-06-01 16:45 ` Kirill Tkhai
2012-06-04 5:27 ` Yong Zhang
2012-11-15 20:35 ` Steven Rostedt
2012-12-18 10:43 ` Kirill Tkhai
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=1334773976.28106.49.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tkhai@yandex.ru \
/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
all inboxes | Powered by JetHome®