From: Peter Zijlstra <peterz@infradead.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
kravetz@us.ibm.com, LKML <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:39:19 +0200 [thread overview]
Message-ID: <1191944359.6848.18.camel@twins> (raw)
In-Reply-To: <1191944024.4281.72.camel@ghaskins-t60p.haskins.net>
On Tue, 2007-10-09 at 11:33 -0400, Gregory Haskins wrote:
> On the flip side: Perhaps sending a reschedule-ipi that doesn't
> reschedule is simply misused, and the misuse should be cleaned up
> instead?
It basically does TIF_WORK_MASK and TIF_NEED_RESCHED is one of the most
frequently used of those. Using it for any other bit in that mask is
IMHO not abuse.
next prev parent reply other threads:[~2007-10-09 15:39 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 ` [PATCH 0/5] RT: scheduler fixes and rt_overload enhancements Peter Zijlstra
2007-10-09 15:00 ` Steven Rostedt
2007-10-09 15:33 ` Gregory Haskins
2007-10-09 15:39 ` Peter Zijlstra [this message]
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=1191944359.6848.18.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox