From: Mike Galbraith <efault@gmx.de>
To: jordan johnston <triplesquarednine@gmail.com>
Cc: Sven-Thorsten Dietrich <sven@thebigcorporation.com>,
Xianghua Xiao <xiaoxianghua@gmail.com>,
"Walzer, Frank" <f-walzer@ti.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.35 RT support roadmap
Date: Fri, 13 Aug 2010 08:14:47 +0200 [thread overview]
Message-ID: <1281680087.8870.82.camel@marge.simson.net> (raw)
In-Reply-To: <AANLkTikoUbL4Q8PNia38AByEfTY56Bqr5uVnyyNxvS1W@mail.gmail.com>
On Thu, 2010-08-12 at 23:17 -0400, jordan johnston wrote:
> > Google did Android and even Palm woke up (just long enough to watch its own
> > demise).
> >
> > The rest is history.
> >
> > Except of course putting the RT Kernel in Android.
>
> As i understand it, many Android users are using the BFS patchset, and
> have been for a while. BFS pretty much does what "the end result of
> using the rt-patches" accomplish, minus rtirq, spin-locks, etc. You
> will get the desired
> responsiveness that using RT would give you.
Heh, RT kernel patch and BFS _scheduler_ patch are not even on the same
planet. BFS is probably not a bad choice for a single cache machine
doing soft RT. I tested it pretty heavily a while back, and it was
generally pretty good.
> Im pretty sure that is why Zen-kernel has a git repository "very
> specifically" for android (BFS is the default kernel setting). I'm
> sure there are other goodies for android in there too.
>
> www.zen-kernel.org
>
> I don't know much about the Android repo's state (as it's fairly new).
> but worth a
> look for your "rt-usage" (ie. performance/responsiveness) for android.
> As i do not own an Android, i have not tested it, but i have talked
> with people who do..
>
> I'm waiting to see what 2.6.35 holds for RT.... but personally i am
> using BFS and 2.6.34 with a lot of performance tuning (a good deal of
> time spent analyzing/tuning) and i am yielding better results not
> using the upstream rt-patches.
> we will see what happens in 2.6.35/36....
It depends on what you're calling performance. A non-rt kernel
absolutely will outperform the rt kernel in many respects. For
instance, if your measure of performance is the time it takes to play
one byte ping-pong over localhost (eg netperf TCP_RR), the rt kernel
will (does) lose badly due to context switch cost between various rt
middle-man threads. If your performance criteria is things like
priority inversion tests, suddenly the comparison does a flipflop.
-Mike
next prev parent reply other threads:[~2010-08-13 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 7:43 2.6.35 RT support roadmap Walzer, Frank
2010-08-12 14:38 ` Xianghua Xiao
2010-08-12 18:38 ` Mike Galbraith
2010-08-12 20:11 ` Sven-Thorsten Dietrich
2010-08-13 3:17 ` jordan johnston
2010-08-13 6:05 ` Sven-Thorsten Dietrich
2010-08-13 9:32 ` jordan johnston
2010-08-13 6:14 ` Mike Galbraith [this message]
2010-08-13 10:51 ` Walzer, Frank
2010-08-17 17:00 ` Clark Williams
2010-08-19 16:09 ` Sven-Thorsten Dietrich
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=1281680087.8870.82.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=f-walzer@ti.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=sven@thebigcorporation.com \
--cc=triplesquarednine@gmail.com \
--cc=xiaoxianghua@gmail.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.