From: "Patel, Vedang" <vedang.patel@intel.com>
To: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
Cc: "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: Mon, 13 Feb 2017 18:48:33 +0000 [thread overview]
Message-ID: <1487011713.17279.27.camel@intel.com> (raw)
In-Reply-To: <20170210190708.gkx5pzxnd6uhfczn@linutronix.de>
On Fri, 2017-02-10 at 20:07 +0100, Sebastian Andrzej Siewior wrote:
> On 2017-02-08 18:41:25 [+0000], Patel, Vedang wrote:
> >
> > Hi,
> Hi,
>
> >
> > The results for the POSIX timers were not as I expected. The
> > latency
> > for real-time kernel (v4.9.4-rt2) was worse compared to the
> > mainline
> > kernel (v4.9.4). In almost all the cases, the latency is almost
> > doubled
> > with the max value reaching about 10 times when performing the
> > tests
> > under load.
> Is it also the case if you boost the priority of ktimersoftd/X
> threads?
> For clock_nanosleep, the wake-ups happen directly from hard-timer
> interrupt. For the posix-timer we have to delay those to the
> ktimersoftd
> thread which runs usually RT prio 1.
>
I am getting very similar results even if I change the priority of
ktimersoftd to 99. Are there any recent rt patches which might have
changed the behaviour of POSIX timers?
Also, are POSIX timers really suited for "real-time" applications?I
believe a similar question was raised by Ran Shalit a few days back:
http://www.spinics.net/lists/linux-rt-users/msg16249.html
Thanks,
Vedang
> >
> > Thanks,
> > Vedang Patel
> > Software Engineer
> > Intel Corporation
> Sebastian
next prev parent reply other threads:[~2017-02-13 18:48 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 [this message]
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
-- 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=1487011713.17279.27.camel@intel.com \
--to=vedang.patel@intel.com \
--cc=bigeasy@linutronix.de \
--cc=darren.hart@intel.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ranshalit@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.