FWIW: I experienced the same problem trying to run trunk on an Airlink101 ar525w (RDC SoC and RAlink card) Comments on my bug report seemed to point at hardware crypto being unsupported and thus eating up all the CPU.
On Sun, Oct 19, 2008 at 2:21 PM, Brian J. Murrell <[EMAIL PROTECTED]>wrote: > On Mon, 2008-10-20 at 07:57 +1100, Andy Botting wrote: > > > > I was doing some iperf tests on it, comparing the difference between > > it, and an older dd-wrt install to see if there was much difference. > > It seemed to be a little slower, but nothing serious. I didn't see > > anything in the logs about softirq. > > I don't think anything shows up in the logs. What you will see, if > anything is that the terminal (i.e. ssh) session you are logged on to > will be very sluggish and the softirq stats can be seen in the header of > a "top" display. > > Try starting top in an ssh session and then running your iperf tests. > > BTW: what throughput did you get on your iperf tests. I could only get > 1.4MB/s before the softirqs bottlenecked the performance. Of course, > 1.4MB/s is only 11.2Mb/s and the client was connected on a 'g' (54Mb/s) > link with no other 'b' in sight, so if the softirqs were not killing it > I should have seen a lot more than 1.4MB/s. > > Cheers, > b. > > > _______________________________________________ > openwrt-users mailing list > [email protected] > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users > >
_______________________________________________ openwrt-users mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
