From: Daniel Wagner <wagi@monom.org>
To: "Remy Böhmer" <linux@bohmer.net>
Cc: linux-rt-users@vger.kernel.org
Subject: HOWTO: Build an RT-application
Date: Tue, 03 Dec 2013 13:58:17 +0100 [thread overview]
Message-ID: <529DD569.2080700@monom.org> (raw)
Hi Remy,
I'd like to update "HOWTO: Build an RT-application" page on
the rt wiki[1]. Since your are listed as maintainer, I better
ask if my ideas are okay before editing.
1) I would like to get rid of quite outdated information (maybe
move it to archive section?) on 'The impact of the Big Kernel Lock'
2) Add 'Don't use priority 99'
3) Don't implement spin locks (use priority inheritance futexes)
4) Avoid slow I/O
5) mmap passing data
6) Be aware of power management: cpufreq, nohz
2) - 5) are stolen from Steven's presentation
cheers,
daniel
[1] https://rt.wiki.kernel.org/index.php/HOWTO:_Build_an_RT-application
[2] http://elinux.org/images/b/ba/Elc2013_Rostedt.pdf
next reply other threads:[~2013-12-03 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 12:58 Daniel Wagner [this message]
[not found] ` <529DD696.7010403@nnytech.net>
2013-12-03 14:03 ` HOWTO: Build an RT-application Daniel Wagner
[not found] ` <CANqCtQK-Q3+ozURx7VBr_xSdjhHNkOm4sYj8KDLRvq=aRBr-kw@mail.gmail.com>
2013-12-16 13:32 ` Daniel Wagner
2014-01-08 22:59 ` John Kacur
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=529DD569.2080700@monom.org \
--to=wagi@monom.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@bohmer.net \
/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).