From: "Heinz Egger" <heinz.egger@linutronix.de>
To: "'David Aldrich'" <David.Aldrich@EMEA.NEC.COM>,
<linux-rt-users@vger.kernel.org>
Subject: AW: Linux RT newbie question
Date: Mon, 8 Feb 2016 16:31:41 +0100 [thread overview]
Message-ID: <013901d16285$cf927770$6eb76650$@linutronix.de> (raw)
In-Reply-To: <41302A7145AC054FA7A96CFD03835A0A0BA8AD12@EX10MBX02.EU.NEC.COM>
Hello David,
there are a number of well known and reputaded companies in the area of
digital audio, video or digital simulation (automotive), just to name a few
areas, which are using a standard PC, Linux and the Preempt-RT patch. With
latencies down to the single-digit microseconds region.
So it is shown that Linux and realtime will work pretty fine here.
br
Heinz
> -----Ursprüngliche Nachricht-----
> Von: linux-rt-users-owner@vger.kernel.org [mailto:linux-rt-users-
> owner@vger.kernel.org] Im Auftrag von David Aldrich
> Gesendet: Montag, 8. Februar 2016 15:28
> An: Stanislav Meduna; linux-rt-users@vger.kernel.org
> Betreff: RE: Linux RT newbie question
>
> Hi Stano
>
> Thanks for your reply ...
>
> > > For a new project we need to demonstrate a Linux RT-Kernel running
> > > a 'standard' x86 desktop PC.
> >
> > What is the goal of this presentation?
>
> The goal is to demonstrate that a communication system previously
> implemented on embedded digital signal processors can be implemented on
> a high spec PC desktop. Sorry that I can't give more details.
>
> > Are you aware that a standard desktop
> > PC might spoil your realtime attempts in various ways (SMI interrupts,
> power
> > management, ...)?
>
> Well, I was not aware of this until reading your email and I read ' HOWTO:
> Build an RT-application' on rt.wiki.kernel.org. The HowTo suggests ways of
> reducing the impact of SMI interrupts. Is this possible?
>
> > > I wonder if a standard Linux distro + RT kernel patch would be a
better
> > choice?
> >
> > As long as you are using a RT kernel, sane pthreads support such as
modern
> > glibc and you know what you are doing (ksoftirqd priority and similar
fun)
> > the particular distribution does not matter much. We are using stock
> Debian
> > with custom kernel as our embedded rt platform.
>
> Do you build your kernel yourselves?
>
> Best regards
>
> David
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -----
> E-Mail ist virenfrei.
> Von AVG überprüft - www.avg.de
> Version: 2015.0.6176 / Virendatenbank: 4522/11563 - Ausgabedatum:
> 05.02.2016
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-08 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 12:16 Linux RT newbie question David Aldrich
2016-02-08 14:03 ` Stanislav Meduna
2016-02-08 14:28 ` David Aldrich
2016-02-08 14:44 ` Stanislav Meduna
2016-02-08 14:50 ` David Aldrich
2016-02-08 15:31 ` Heinz Egger [this message]
2016-02-08 14:25 ` Ralf Mardorf
2016-02-08 14:31 ` David Aldrich
2016-02-08 14:42 ` Ralf Mardorf
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='013901d16285$cf927770$6eb76650$@linutronix.de' \
--to=heinz.egger@linutronix.de \
--cc=David.Aldrich@EMEA.NEC.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).