From: Mike Galbraith <bitbucket@online.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: rt: rtmutex experiment doubled tbench throughput
Date: Wed, 27 Feb 2013 05:55:00 +0100 [thread overview]
Message-ID: <1361940900.4599.108.camel@marge.simpson.net> (raw)
In-Reply-To: <1361932513.11373.65.camel@gandalf.local.home>
On Tue, 2013-02-26 at 21:35 -0500, Steven Rostedt wrote:
> On Tue, 2013-02-26 at 21:32 -0500, Steven Rostedt wrote:
>
> > Bah! As I looked in my history I see I did the following:
> >
> > git show v3.0:include/linux/sched.h
> > git show v3.2:include/linux/sched.h
> > git show v3.4:include/linux/sched.h
> >
> > I forgot the '-rt" on each one of them :-p
>
> That said...
>
> Only v3.0-rt has it. I'm barely supporting that now, and I'm only doing
> updates that might make sense. Greg should be dropping it soon, and so
> will I. There's issues in v3.0-rt that are not in v3.2-rt or above, that
> I'm not going to bother debugging.
Yeah, I'm stuck with 3.0, so my 3.0 is not as virgin as I would like it
to be. It has threaded sirqs because I must have them, can turn cpupri
and nohz on/off on the fly because I must have to have that too to make
80 core boxen with tight jitter constraint be all they can be.
> I'll test a patch against the others but not one against v3.0-rt.
64 core test box has microscopic root and newer kernel drivers break its
userspace. Putting a newer rt kernel on it to play is a pita, so I do
big box tinkering in 3.0. I can make a 3.6 hacklet during the weekend.
-Mike
prev parent reply other threads:[~2013-02-27 4:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 16:36 rt: rtmutex experiment doubled tbench throughput Mike Galbraith
2013-02-23 8:25 ` Mike Galbraith
2013-02-26 19:45 ` Steven Rostedt
2013-02-27 4:19 ` Mike Galbraith
2013-02-28 5:59 ` Mike Galbraith
2013-02-26 21:25 ` Steven Rostedt
2013-02-27 2:22 ` Paul Gortmaker
2013-02-27 2:32 ` Steven Rostedt
2013-02-27 2:35 ` Steven Rostedt
2013-02-27 2:52 ` Paul Gortmaker
2013-02-27 4:55 ` Mike Galbraith [this message]
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=1361940900.4599.108.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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