2013/8/9 Rafał Miłecki <zaj...@gmail.com>: > 2013/8/8 Hauke Mehrtens <ha...@hauke-m.de>: >>> Should I play with some profiler? >>> /proc/profile (and readprofile user space tool) doesn't support >>> profiling modules :( >> >> You can compile bgmac into the kernel, the results you get should be the >> same as you would get for the module. You just have to change >> target/linux/brcm47xx/config-3.10 . > > I built bgmac as a part of the kernel image and added System.map in > the following way: >> make V=s >> mkdir target/linux/generic/base-files/boot/ >> cp >> build_dir/target-mipsel_uClibc-0.9.33.2/linux-brcm47xx/linux-3.6.11/System.map >> target/linux/generic/base-files/boot/ >> make V=s > > Then I tried profiling iperf client with the following command: > readprofile -r; iperf -c 192.168.1.218; readprofile | sort -nr > Unfortunately this resulted in 515 *unknown*, I'm not sure about this part. > > Apart from that there are many calls to the > __copy_user_common > > Please note I run "iperf -c" in the OpenWrt, so it was mostly doing > only TX (not much RX).
I did reverse test running "iperf -s" on OpenWrt and "iperf -c" on LAN machine. It's interesting that I got quite higher results, instead of 87Mb/s I got 155Mb/s. It seems OpenWrt prefers to receive than transmit, that's interesting... In this case I got: 598 __copy_user_common 0.8592 576 *unknown* 281 csum_partial 0.1968 The command I used: # readprofile -r; iperf -s; readprofile | sort -nr (I had to CTRL+C as soon as iperf transfer has finished) Attaching full log. -- Rafał
readprofile.log
Description: Binary data
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
