ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT
Date: Wed, 14 Oct 2015 22:20:02 -0400	[thread overview]
Message-ID: <20151014222002.3f345ac3@grimm.local.home> (raw)
In-Reply-To: <561EAD4D.6080901@sonymobile.com>

On Wed, 14 Oct 2015 12:30:21 -0700
Tim Bird <tim.bird@sonymobile.com> wrote:

REPLY ALL Tim! I didn't notice this email till I saw it as QotW on LWN.


> Check out Xenomai. (xenomai.org)  I think that's what many embedded folk use
> if they find that RT-PREEMPT does not meet their needs.  Xenomai 3.0
> allows you to use their system either on top of RT-PREEMPT or
> on top of their Cobalt kernel sitting next to (or in front of,
> depending on your perspective) the Linux kernel.
> 
> Sony used RT-PREEMPT in some products, and a dual-kernel in others,
> and isolated CPUs running something else (usually uItron) in yet others.
> 
> Personally, I'd be happy to see RT-PREEMPT go in - there are certain use

BTW, it's PREEMPT_RT not RT-PREEMPT.

> cases for it.  I'd also like to see the NOHZ stuff go in as well.  It should
> solve a set of problems for isolating RT tasks without sacrificing
> performance on the non-RT CPUs.  And finally, I wouldn't mind putting
> a non-Linux RT kernel like Cobalt (oh the horrors) into mainline as well.
> Each of these approaches has their strengths and weaknesses.  Linux is,
> after all, whatever we say it is - and it could easily have a small RT
> micro-kernel as part of the source base as well.
> 
> AFAIK the patent issues that plagued the dual-kernel approach are now
> behind us, so this might be a good area of investigation.
> 
> I've long felt that RT-PREEMPT was sucking the oxygen out of getting other,
> technically valid, approaches to RT with Linux into mainline.

I'm perfectly fine with working together with Xenomai. When you need a
few microsecond latencies, that may be the best tool. I don't think
they are mutually exclusive, but actually complement each other quite
nicely.

-- Steve

  reply	other threads:[~2015-10-15  2:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 16:42 Steven Rostedt
2015-10-13 17:33 ` Josh Triplett
2015-10-13 22:40 ` Rafael J. Wysocki
2015-10-13 22:19   ` Luis R. Rodriguez
2015-10-13 22:39     ` Steven Rostedt
2015-10-13 22:48       ` Luis R. Rodriguez
2015-10-13 23:04     ` Rafael J. Wysocki
2015-10-13 22:41       ` Luis R. Rodriguez
2015-10-14  7:35 ` Linus Walleij
2015-10-14 11:45 ` Christoph Lameter
2015-10-14 13:20   ` Steven Rostedt
2015-10-14 14:49     ` Christoph Lameter
2015-10-14 15:22       ` Steven Rostedt
2015-10-14 18:12         ` Christoph Lameter
2015-10-14 18:32           ` Steven Rostedt
2015-10-14 18:56             ` Christoph Lameter
2015-10-14 19:17               ` James Bottomley
2015-10-14 19:30               ` Tim Bird
2015-10-15  2:20                 ` Steven Rostedt [this message]
2015-10-15  9:05                 ` Thomas Gleixner
2015-10-14 20:24               ` Thomas Gleixner
2015-10-15 14:22                 ` Christoph Lameter
2015-10-15 15:13                   ` Steven Rostedt
2015-10-15 17:21                     ` Jan Kara
2015-10-15 18:09                       ` Steven Rostedt
2015-10-15 20:21                   ` Thomas Gleixner
2015-10-15 20:37                     ` Thomas Gleixner
2016-08-05 22:32 ` Darren Hart
2016-08-05 22:40   ` Darren Hart

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=20151014222002.3f345ac3@grimm.local.home \
    --to=rostedt@goodmis.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tim.bird@sonymobile.com \
    /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