From: "Gregory Haskins" <ghaskins@novell.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Dmitry Adamushko" <dmitry.adamushko@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 2/2] sched: prioritize non-migratable tasks over migratableones
Date: Wed, 23 Apr 2008 07:11:42 -0600 [thread overview]
Message-ID: <480EFD4E.BA47.005A.0@novell.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0804230854210.23815@gandalf.stny.rr.com>
>>> On Wed, Apr 23, 2008 at 8:58 AM, in message
<Pine.LNX.4.58.0804230854210.23815@gandalf.stny.rr.com>, Steven Rostedt
<rostedt@goodmis.org> wrote:
>
> I'm not giving an Ack on this patch (not yet). My main concern here is
> that this is performing on a verge of policy change. As you stated, this
> is a known issue. One that can be avoided by giving RT tasks different
> priorities. It is known that two tasks with the same priority fighting
> for the same CPUS (even if one is migratable and one is not) has
> non-deterministic behaviour.
>
> This patch needs a bit of running through the grind to see what effects it
> has before going in.
Perfectly reasonable stance, Steve. Thanks for the review!
-Greg
next prev parent reply other threads:[~2008-04-23 13:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 18:10 [PATCH 0/2] sched: refreshes Gregory Haskins
2008-04-21 18:10 ` [PATCH 1/2] sched: push rt tasks only if newly activated tasks have been added Gregory Haskins
2008-04-22 15:30 ` Dmitry Adamushko
2008-04-22 15:51 ` Steven Rostedt
2008-04-23 8:05 ` Dmitry Adamushko
2008-04-23 9:53 ` Dmitry Adamushko
2008-04-23 10:03 ` Gregory Haskins
2008-04-23 10:03 ` Gregory Haskins
2008-04-23 10:23 ` Dmitry Adamushko
2008-04-23 10:54 ` Gregory Haskins
2008-04-23 10:54 ` Gregory Haskins
2008-04-23 11:20 ` Dmitry Adamushko
2008-04-22 16:38 ` Gregory Haskins
2008-04-23 11:13 ` [RFC PATCH 0/2] sched fixes for suboptimal balancing Gregory Haskins
2008-04-23 11:13 ` [PATCH 1/2] sched: fix RT task-wakeup logic Gregory Haskins
2008-04-23 11:13 ` Gregory Haskins
2008-04-23 12:54 ` Steven Rostedt
2008-04-23 14:29 ` Dmitry Adamushko
2008-04-24 11:56 ` Gregory Haskins
2008-04-28 16:30 ` [(RESEND) PATCH] " Gregory Haskins
2008-04-28 16:30 ` Gregory Haskins
2008-04-29 14:35 ` Ingo Molnar
2008-04-23 11:13 ` [PATCH 2/2] sched: prioritize non-migratable tasks over migratable ones Gregory Haskins
2008-04-23 12:58 ` Steven Rostedt
2008-04-23 13:11 ` Gregory Haskins [this message]
2008-04-28 18:55 ` [RFC PATCH 0/2] sched fixes for suboptimal balancing Ingo Molnar
2008-04-21 18:10 ` [PATCH 2/2] sched: Use a 2-d bitmap for searching lowest-pri CPU Gregory Haskins
2008-04-21 19:33 ` [PATCH 0/2] sched: refreshes Ingo Molnar
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=480EFD4E.BA47.005A.0@novell.com \
--to=ghaskins@novell.com \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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.