From: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Real time kernel
Date: Mon, 12 Oct 2009 23:04:55 +0200 [thread overview]
Message-ID: <2d05c4580910121404x7d09ea3dvde1aa49b05d2e3fc@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0910121615100.5363@gentwo.org>
This is definition from http://rt.wiki.kernel.org/
-------------------------------------------------------------------------
Real-time applications have operational deadlines between some
triggering event and the application's response to that event. To meet
these operational deadlines, programmers use real-time operating
systems (RTOS) on which the maximum response time can be calculated or
measured reliably for the given application and environment.
-------------------------------------------------------------------------
So for specific requirements I would not say, you get slower kernel,
you get purpose-making kernel, because on these kind of systems you
probably do not do anything. It is probably the system that listens
and responds to some events.
Do you want to say, when using preemption in "normal user mode", Linux
works slower then without preemption ?
It makes sense,
"because the latency of a task only depends on the tasks running at
equal or higher priorities, all other tasks can be ignored."
(http://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions#What_is_real-time.3F)
Thanks
next prev parent reply other threads:[~2009-10-12 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 18:00 Dragoslav Zaric
2009-10-12 18:20 ` Thomas Backlund
2009-10-12 20:16 ` Christoph Lameter
2009-10-12 21:04 ` Dragoslav Zaric [this message]
2009-10-12 21:08 ` Christoph Lameter
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=2d05c4580910121404x7d09ea3dvde1aa49b05d2e3fc@mail.gmail.com \
--to=dragoslav.zaric.kd@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®