From: "Chris Friesen" <cfriesen@nortel.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: mingo@elte.hu, rostedt@goodmis.org, peterz@infradead.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Series short description
Date: Tue, 11 Nov 2008 13:31:39 -0600 [thread overview]
Message-ID: <4919DD9B.1070104@nortel.com> (raw)
In-Reply-To: <20081111142323.28477.41235.stgit@dev.haskins.net>
Gregory Haskins wrote:
> Hi Ingo, Steven, Peter,
> This series applies roughly to mainline as an enhancement to the sched_rt
> logic. Peter and I were discussing some of the unecessary overhead in
> pull_rt_tasks() via IRC, and this is my RFC attempt to address the problem.
>
> I have built/booted this on a 4-way C2D Xeon box and it passes preempt-test.
At first blush it looks reasonable, but do you have any performance numbers?
Chris
next prev parent reply other threads:[~2008-11-11 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 14:26 [RFC PATCH 0/3] Series short description Gregory Haskins
2008-11-11 14:26 ` [RFC PATCH 1/3] sched: track the next-highest priority on each runqueue Gregory Haskins
2008-11-11 14:26 ` [RFC PATCH 2/3] sched: use highest_prio.curr for pull threshold Gregory Haskins
2008-11-11 14:26 ` [RFC PATCH 3/3] sched: use highest_prio.next to optimize pull operations Gregory Haskins
2008-11-11 17:56 ` [RFC PATCH 0/3] Series short description Ingo Molnar
2008-11-11 18:51 ` Gregory Haskins
2008-11-11 19:31 ` Chris Friesen [this message]
2008-11-11 19:50 ` Gregory Haskins
[not found] ` <4936E587.40700@gmail.com>
[not found] ` <4936EC83.2060900@oracle.com>
2008-12-03 20:39 ` [RFC PATCH 0/3] sched: track next-highest priority (was "Series short discription") Gregory Haskins
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=4919DD9B.1070104@nortel.com \
--to=cfriesen@nortel.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).