From: jordan <triplesquarednine@gmail.com>
To: John Kacur <jkacur@redhat.com>
Cc: Gautam Thaker <gautam.h.thaker@lmco.com>, linux-rt-users@vger.kernel.org
Subject: Re: "yum install ...." based instruction on building a RT kernel.
Date: Sat, 18 Sep 2010 16:06:45 -0400 [thread overview]
Message-ID: <AANLkTi==4a5VpUszHC23WOGkM-fdos3x2M0P-ygRdttx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikv7cmA_F==TKa1m0o_N1OHxp3RgXXMErhcgGM0@mail.gmail.com>
Hi John,
I forgot number 5....
Once, you have a working rt-kernel, read up the linux schedulers (ie:
CFS and CFQ). Then, tune those as well.
As you would know working for redhat, these can be tuned after the
kernel is compiled. There are methods to do this littered all over the
internet. You can use all sorts of tools (cyclictest/signaltest/etc)
to accurately see what effect your changes are making...then you test
with your applications for "real-world" tests/performance.
So, there is a learning curve. I would be lying, if i didn't
acknowledge this, But once you have done it a few times, it is
knowledge that you have, and won't have to re-learn. Then, it becomes
very simple to do. (this applies to everything i wrote about)
jordan
prev parent reply other threads:[~2010-09-18 20:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 22:54 "yum install ...." based instruction on building a RT kernel Gautam Thaker
2010-09-17 6:08 ` jordan
2010-09-17 7:08 ` John Kacur
2010-09-17 12:38 ` Daniel James
2010-09-17 13:06 ` Bernardo Barros
2010-09-17 15:25 ` EXTERNAL: " Gautam Thaker
2010-09-18 19:34 ` jordan
2010-09-17 13:10 ` John Kacur
2010-09-18 19:24 ` jordan
2010-09-19 15:49 ` Clark Williams
2010-09-19 17:23 ` jordan
2010-09-19 19:20 ` Bernardo Barros
2010-09-19 20:00 ` jordan
2010-10-17 15:20 ` jordan
2010-10-18 6:16 ` John Kacur
2010-10-18 7:12 ` jordan
2010-09-18 19:15 ` jordan
2010-09-18 20:06 ` jordan [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='AANLkTi==4a5VpUszHC23WOGkM-fdos3x2M0P-ygRdttx@mail.gmail.com' \
--to=triplesquarednine@gmail.com \
--cc=gautam.h.thaker@lmco.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.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).