public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tracy Smith <tlsmith3777@gmail.com>
Cc: "bigeasy@linutronix.de" <bigeasy@linutronix.de>,
	"Patel, Vedang" <vedang.patel@intel.com>,
	"julia@ni.com" <julia@ni.com>,
	"ranshalit@gmail.com" <ranshalit@gmail.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	"Hart, Darren" <darren.hart@intel.com>
Subject: Re: Regression on rt kernel while using POSIX timers
Date: Fri, 3 Mar 2017 17:51:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1703031733570.4522@nanos> (raw)
In-Reply-To: <472B70D9-E1AF-4D14-BE79-ABAAC74BA4DB@gmail.com>

On Wed, 1 Mar 2017, Tracy Smith wrote:

First of all, please do not top post and trim your replies.

> Pleaee isolate the specific release where latency regression occurred if
> the community has not already done so.

Which regression are you talking about?

> Possibly backing out changes specific to timers and posix threads for
> that release to see what impacted latency.

The issue Vedang and Sebastian are discussing is a configuration
problem. Backing out changes should really solve that.

> This is crucial for NXP and others as they migrate to later releases of
> the kernel.

Thanks for the enlightment, we really were unaware about the crucial
importance.

       tglx

  parent reply	other threads:[~2017-03-03 17:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 18:41 Regression on rt kernel while using POSIX timers Patel, Vedang
2017-02-10 19:07 ` Sebastian Andrzej Siewior
2017-02-13 18:48   ` Patel, Vedang
2017-02-15 16:54     ` bigeasy
2017-02-16  2:05       ` Julia Cartwright
2017-02-16  2:34         ` Patel, Vedang
2017-02-22  1:43           ` Patel, Vedang
2017-03-01 15:22             ` bigeasy
2017-03-01 19:03               ` Tracy Smith
2017-03-02  3:23                 ` Patel, Vedang
2017-03-03 19:41                   ` Julia Cartwright
2017-03-03 20:32                     ` Julia Cartwright
2017-03-03 21:09                     ` Thomas Gleixner
2017-03-03 23:36                       ` Patel, Vedang
2017-03-06 11:29                         ` Thomas Gleixner
2017-03-07  2:01                           ` Patel, Vedang
2017-03-07 17:03                             ` Thomas Gleixner
2017-03-20 22:54                               ` Patel, Vedang
2017-03-03 16:51                 ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-13 20:32 Ran Shalit

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.DEB.2.20.1703031733570.4522@nanos \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=darren.hart@intel.com \
    --cc=julia@ni.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ranshalit@gmail.com \
    --cc=tlsmith3777@gmail.com \
    --cc=vedang.patel@intel.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