From: Peter Zijlstra <peterz@infradead.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: mingo@elte.hu, linux-rt-users@vger.kernel.org,
rostedt@goodmis.org, kravetz@us.ibm.com,
linux-kernel@vger.kernel.org, pmorreale@novell.com,
sdietrich@novell.com
Subject: Re: [PATCH 0/5] RT: scheduler fixes and rt_overload enhancements
Date: Tue, 09 Oct 2007 17:00:29 +0200 [thread overview]
Message-ID: <1191942029.6848.15.camel@twins> (raw)
In-Reply-To: <20071009142044.4941.65189.stgit@novell1.haskins.net>
On Tue, 2007-10-09 at 10:25 -0400, Gregory Haskins wrote:
> Hi All,
>
> The first two patches are from Mike and Steven on LKML, which the rest of my
> series is dependent on. Patch #4 is a resend from earlier.
>
> Series Summary:
>
> 1) Send IPI on overload regardless of whether prev is an RT task
> 2) Set the NEEDS_RESCHED flag on reception of RESCHED_IPI
> 3) Fix a mistargeted IPI on overload
> 4) Track which CPUS are in overload for efficiency
> 5) Track which CPUs are eligible for rebalancing for efficiency
>
> These have been built and boot-tested on a 4-core Intel system.
Ok, I'm not liking these.
I really hate setting TIF_NEED_RESCHED from the IPI handler. Also, I
don't see how doing a resched pulls tasks to begin with.
How about keeping a per rq variable that indicates the highest priority
of runnable tasks. And on forced preemption look for a target rq to send
your last highest task to.
There is no need to broadcast rebalance, that will only serialise on the
local rq lock again. So pick a target rq, and stick with that.
Also, I think you meant to use cpus_and() with the rto and allowed
masks.
next prev parent reply other threads:[~2007-10-09 15:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 14:25 [PATCH 0/5] RT: scheduler fixes and rt_overload enhancements Gregory Haskins
2007-10-09 14:25 ` [PATCH 1/5] RT - fix for scheduling issue Gregory Haskins
2007-10-09 14:25 ` [PATCH 2/5] RT - fix reschedule IPI Gregory Haskins
2007-10-09 14:25 ` [PATCH 3/5] RT - fix mistargeted RESCHED_IPI Gregory Haskins
2007-10-09 14:26 ` [PATCH 4/5] RT: Add a per-cpu rt_overload indication Gregory Haskins
2007-10-09 14:26 ` [PATCH 5/5] RT - Track which CPUs should get IPI'd on rt-overload Gregory Haskins
2007-10-09 15:00 ` Peter Zijlstra [this message]
2007-10-09 15:00 ` [PATCH 0/5] RT: scheduler fixes and rt_overload enhancements Steven Rostedt
2007-10-09 15:33 ` Gregory Haskins
2007-10-09 15:39 ` Peter Zijlstra
2007-10-09 17:59 ` [RFC PATCH RT] push waiting rt tasks to cpus with lower prios Steven Rostedt
2007-10-09 18:14 ` Steven Rostedt
2007-10-09 18:16 ` Peter Zijlstra
2007-10-09 18:45 ` Steven Rostedt
2007-10-09 20:39 ` mike kravetz
2007-10-09 20:50 ` Steven Rostedt
2007-10-09 21:17 ` mike kravetz
2007-10-10 2:12 ` Girish kathalagiri
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=1191942029.6848.15.camel@twins \
--to=peterz@infradead.org \
--cc=ghaskins@novell.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pmorreale@novell.com \
--cc=rostedt@goodmis.org \
--cc=sdietrich@novell.com \
/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.