Steven Rostedt wrote:It builds and runs fine on my Icecube-MPC5200 board, now also with the latency tracer enabled. That's great. Still, "cyclictest -n -p80 -i1000" reports latencies up to 400 us and therefore I tried to trigger and save a high latency trace using: # ./cyclictest -n -p80 -i1000 -b400 1.21 0.33 0.11 4/42 1048 T: 0 ( 914) P:80 I:1000 C: 38726 Min: 61 Act: 107 Avg: 106 Max: 377 [ 91.042169] ( cyclictest-914 |#0): new 39733427 us user-latency. bash-3.00# cat /proc/latency_trace > trace.log Well, I'm not sure if this is the correct way to do it. Is there some doc on how to use the latency tracer and interpret the results? Nevertheless, I have attached the beginning of trace.log. Maybe it rings an experts bell. TIA. Wolfgang.
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
