ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Christoph Lameter <cl@linux.com>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT
Date: Thu, 15 Oct 2015 19:21:39 +0200	[thread overview]
Message-ID: <20151015172139.GA14167@quack.suse.cz> (raw)
In-Reply-To: <20151015111310.01903df1@gandalf.local.home>

On Thu 15-10-15 11:13:10, Steven Rostedt wrote:
> On Thu, 15 Oct 2015 09:22:58 -0500 (CDT)
> Christoph Lameter <cl@linux.com> wrote:
> 
> > I have no particular use case for my company in mind here. This is what I
> > hear when talking to various companies in a number of different areas of
> > computing that have tried preempt_rt.
> 
> Why are they telling you this and not us? Of course this may be people
> that have different requirements.
> 
> Need a few microsecond latencies; Try Xenomai.
> Need a few hundred microsecond latencies; PREEMPT_RT will do
> Need no interference from the kernel; Use NO_HZ_FULL
> 
> Look, there's obviously users of PREEMPT_RT, so why are you trying to
> kill it? If anything, PREEMPT_RT has made the mainline kernel cleaner.
> 
> Just because you don't see a use for it, doesn't mean one does not
> exist.

I know close to nothing about RT so maybe a stupid question: Do I
understand correctly that PREEMP_RT is there for use cases where processes
have latency requirements but also need to do syscalls as a part of their
work? Or is it that we cannot afford to isolate kernel on some CPUs because
it's too hard to estimate how much work it will need to do, it wastes too
much etc.? Or both?

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2015-10-15 17:21 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
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 [this message]
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=20151015172139.GA14167@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=cl@linux.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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