On Monday 05 October 2009, Arjan van de Ven wrote: > On Mon, 5 Oct 2009 16:13:31 +0200 Frans Pop <elendil@xxxxxxxxx> wrote: > > On Monday 05 October 2009, Frans Pop wrote: > > > With .32-rc3 I'm getting occasional skips from amarok while playing > > > music from an NFS share (3 today so far), something I've not had in > > > a long time. > > > > > > The reason looks to be that latencytop consistently shows 'iwlagn' > > > as the top affected process with "Scheduler: waiting for CPU". > > > Values of 100-140 ms occur frequently, but I've also seen higher > > > values (180, 207). I don't remember seeing iwlagn high in the list > > > before, but I have not checked earlier kernels yet. > > > > > > Added to that 'phy0' also frequently shows high with values of > > > 25-75 ms. I've checked for 2.6.31.1 now and iwlagn is listed high there too when the system is idle, but with normal values of 60-100 ms. And phy0 has normal values of below 10 ms. I've now rebooted with today's mainline git; phy0 now frequently shows with values of around 100 ms too (i.e. higher than last time). Both still go way down as soon as the system is given work to do. > > If I give the system some work to do (like compiling a kernel), the > > latencies on iwlagn and phy0 disappear (values < 5 ms). > > Is this related to ondemand frequency scaling? > > shouldn't be.... but > > can you do a 5 second or so timechart recording of this? > That will capture all scheduler delays as well as the P states etc.... With a 5 second sleep I was unable to get any significant latencies (I started perf on a latencytop refresh and did a manual refresh as it finished to see what happened during the perf run). The perf run does seem to affect the latencies. I've uploaded a chart for a 10s sleep during which I got latencies of 101ms for iwlagn and 77ms for phy0: http://people.debian.org/~fjp/tmp/kernel/. I've also uploaded the raw data as the colors in the chart looked off to me (CPU bars were mostly black in Debian unstable's inkscape). I can't make much from the chart TBH, but maybe you can. Not sure what to do with this. For now I'd suggest to ignore it as it's all a bit vague. Unless of course you feel the latencies are higher than they should be. I'll see if I get more skips and what latencies I get during them. Cheers, FJP -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
