From: Gregory Haskins <ghaskins@novell.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Gregory Haskins <ghaskins@novell.com>
Subject: [PATCH 0/4] RT: RT-Overload/Sched v3
Date: Tue, 16 Oct 2007 12:08:52 -0400 [thread overview]
Message-ID: <20071016160226.5202.53965.stgit@novell1.haskins.net> (raw)
v3 contains the following changes since v2:
This is still based on 23-rt1 + Steve's last public patch (I think Steve has a
newer version available, but we have not rebased yet).
1) No longer includes the per-cpu-rtoverload patch, since Steve has already
ACKed it
2) Dropped the affinity patch because it was buggy. Will revisit later
3) Dropped the pull-patch, since it was RFC only anyway. Will revisit later
4) Addressed review comments/feedback (added patch descriptions across the
board, moved semi-colon in while loop, removed superfluous
smp_processor_id() etc.
5) Got rid of the second TASK_PREEMPTS_CURR() check, since my anaylsys
determined it was not needed.
With this patch series applied, my RT test now passes and we get an average of
23us wake-up latency under load. You can find the test here:
ftp://ftp.novell.com/dev/ghaskins/preempt.cc
Note: Do not use the "affinity" option, as the validator has a bug related to
it and may yield a false negative.
Regards,
-Greg
next reply other threads:[~2007-10-16 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 16:08 Gregory Haskins [this message]
2007-10-16 16:08 ` [PATCH 1/4] RT: Wrap the RQ notion of priority to make it conditional Gregory Haskins
2007-10-16 16:09 ` [PATCH 2/4] RT: Initialize the priority value Gregory Haskins
2007-10-16 16:09 ` [PATCH 3/4] RT: Add support for updating push-rt priority under PI boost Gregory Haskins
2007-10-16 16:09 ` [PATCH 4/4] RT: Add support for low-priority wake-up to push_rt feature 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=20071016160226.5202.53965.stgit@novell1.haskins.net \
--to=ghaskins@novell.com \
--cc=a.p.zijlstra@chello.nl \
--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 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®