From: Tim Sander <tim@krieglstein.org>
To: Martin.Wirth@dlr.de
Cc: linux-rt-users@vger.kernel.org
Subject: Re: AW: Large latencies with 4.4.1-rt6
Date: Thu, 25 Feb 2016 13:52:21 +0100 [thread overview]
Message-ID: <7328385.lupKz22AGa@dabox> (raw)
In-Reply-To: <1A2AF5F768264E479963C4D8C015EB691B6973E6@dlrexmbx03.intra.dlr.de>
Hi Martin
Am Donnerstag, 25. Februar 2016, 12:47:31 schrieb Martin.Wirth@dlr.de:
> > I have also seen a latency increase with 4.4.1-rtX releases. I have the
> > impression that some stable kernel updates made it worse. Care to test
> > 4.4-
> > rt3 or 4.4-rt4? Had not the chance to pin them down by now.
>
> The worst case cyclictest latencies (running over serveral hours) with pre
> 4.4.x-rt versions were below 10 µs for an idle system and below 23 µs for a
> kernel compile with make -j4. Since this is a machine with is in lab-use
> during the day I hesitate a bit to try too early 4.4.x version which might
> be instable enough to eat my disk.
Well the 4.4 releases have been pretty stable for me on ARM but your milage
may by different...
Best regards
Tim
--
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-25 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 17:02 Large latencies with 4.4.1-rt6 Martin.Wirth
2016-02-25 12:34 ` Tim Sander
2016-02-25 12:47 ` AW: " Martin.Wirth
2016-02-25 12:52 ` Tim Sander [this message]
2016-02-25 15:29 ` Sebastian Andrzej Siewior
2016-02-25 16:08 ` AW: " Martin.Wirth
2016-02-25 16:29 ` Sebastian Andrzej Siewior
2016-02-29 17:02 ` AW: " Martin.Wirth
2016-02-29 21:05 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2016-03-01 10:21 Martin.Wirth
2016-03-04 7:40 Martin.Wirth
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=7328385.lupKz22AGa@dabox \
--to=tim@krieglstein.org \
--cc=Martin.Wirth@dlr.de \
--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).