linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Mark Hounschell <dmarkh@cfl.rr.com>
Cc: Anisha Kaul <born.rebel.83@gmail.com>, linux-rt-users@vger.kernel.org
Subject: Re: Hard real time in user space with preempt_rt patch
Date: Tue, 24 Apr 2012 13:36:09 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204241331550.3182@tycho> (raw)
In-Reply-To: <4F966AFC.7070803@cfl.rr.com>



On Tue, 24 Apr 2012, Mark Hounschell wrote:

> On 04/24/2012 01:46 AM, Anisha Kaul wrote:
> > From:
> > https://rt.wiki.kernel.org/articles/f/r/e/Frequently_Asked_Questions_7407.html
> > 
> > > Real-time only has impact on the kernel; Userspace does not notice the
> > > difference except for better real time behavior.
> > 
> > Does it mean that if we write the applications in user space, they
> > won't get the hard real time effect?
> > The threads running in the userspace won't get the hard real time effect?
> > 
> 
> You use the term "hard real time". The RT patch set does not even come close
> to providing a "hard real time" environment, and isn't even attempting to.

Wrong. It is attempting to come as close to hard real-time responses as 
possible. There is however, no mathematical guarantee that it will do so, 
that some would require of "hard real time". What exactly is meant by hard 
real time is also a bit hard to pin down. For a good easy to 
read discussion of it, 
check out http://www.linuxjournal.com/article/9361

> does however provide user land applications a much better chance for a "soft
> real time" environment. The phrase you quot above just means the patches are
> applied to the kernel and there are no patches required for user land glibc or
> your application.

That sounds right to me.

      parent reply	other threads:[~2012-04-24 11:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  5:46 Hard real time in user space with preempt_rt patch Anisha Kaul
2012-04-24  6:05 ` raz ben yehuda
2012-04-24  8:57 ` Mark Hounschell
     [not found]   ` <CAF-VNaq3bkC=LCB-Emsx20xTm-Vm1v3kduC5MpyXQA_GS6SOhg@mail.gmail.com>
2012-04-24  9:42     ` Mark Hounschell
2012-04-24 16:26       ` Sven-Thorsten Dietrich
2012-04-24 17:25         ` Mark Hounschell
2012-04-24 19:20           ` Lars Segerlund
2012-04-30 13:18             ` Esben Nielsen
2012-04-24 19:37       ` Armin Steinhoff
2012-04-24 11:36   ` John Kacur [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=alpine.LFD.2.02.1204241331550.3182@tycho \
    --to=jkacur@redhat.com \
    --cc=born.rebel.83@gmail.com \
    --cc=dmarkh@cfl.rr.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).