linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Sander <tim@krieglstein.org>
To: Matthias Fuchs <mfuchs@ma-fu.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: 3.12.6-rt9 on AM335x (armv7)
Date: Tue, 07 Jan 2014 09:38:49 +0100	[thread overview]
Message-ID: <15611103.51LOkxSQt9@dabox> (raw)
In-Reply-To: <52CB0881.9000502@ma-fu.de>

Hi
> after some chatting with Nicholas and being sure that I didn't do anything
> totally stupid I would like to provide my current kernel config and a trace
> generated by "cyclictest ... -b500".
> 
> kernel config -> https://www.dropbox.com/s/zsud0b77xoosjm1/config
> trace ->
> https://www.dropbox.com/s/5uf58oqo0qwcn4x/trace-cyclictest-2508us.txt
> 
> I still get max latencies of about 4000us on this TI AM335x system running
> 3.12.6-rt9 with timers-do-not-raise-softirq-unconditionally.patch reverse
> applied.
> 
> sched_rt_runtime_us and sched_rt_period_us are identical. The system is idle
> during the test. Rootfilesystem comes via NFS.
> 
> root@generic-armv7a:~# cat /proc/sys/kernel/sched_rt_runtime_us
> 1000000
> root@generic-armv7a:~# cat /proc/sys/kernel/sched_rt_period_us
> 1000000
> 
> root@generic-armv7a:~# uname -a
> Linux generic-armv7a 3.12.6-rt9-dirty #3 SMP PREEMPT RT Sat Jan 4 23:01:19
> CET 2014 armv7l GNU/Linux
> 
> root@generic-armv7a:~# ~/cyclictest -p99 -m -n -i200 -h400 -q -l100000 -b
> 500 # /dev/cpu_dma_latency set to 0us
> INFO: debugfs mountpoint: /sys/kernel/debug/tracing/
> could not set ftrace_enabled to 0
> could not set tracing_max_latency to 0
> # Histogram
> ...
> # Total: 000018604
> # Min Latencies: 00024
> # Avg Latencies: 00158
> # Max Latencies: 02508
Wohaa, thats bad for a latency patched kernel. Have you disabled 
powermanagement? I have an older rt patched kernel and it was not too good.
If i remember correctly it was between 100-200µs latency. But thats
far better than this. You could also load the system with hackbench, if its 
the idle pm than latency would get better.

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

  reply	other threads:[~2014-01-07  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 16:37 3.12.6-rt9 on AM335x (armv7) Matthias Fuchs
2014-01-06 19:48 ` Matthias Fuchs
2014-01-07  8:38   ` Tim Sander [this message]
2014-01-07 21:20     ` Matthias Fuchs
2014-01-07 22:58       ` Tim Sander
2014-01-07 23:46         ` Pavel Vasilyev
2014-01-08  8:08           ` Matthias Fuchs
2014-01-08  8:06         ` Matthias Fuchs
2014-02-07 16:07           ` Sebastian Andrzej Siewior

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=15611103.51LOkxSQt9@dabox \
    --to=tim@krieglstein.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mfuchs@ma-fu.de \
    /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).