Hi, > My colleague just tested this patch set and found out that the in > question makes our 400MHz ARM cpu board with ralink usb dongle non > functional due to high cpu consumption. it seems for us that exiting > from function every time it finds an entry is too expensive on systems > slower than PCs. Interesting, I would suspected the patch to reduce the CPU consumption rather then increasing it. I can do some testing regarding this looping during the weekend, but I haven't seen high CPU consumption on my system during my last test. However I wasn't testing on an embedded system... > To verify our thought, we changed the source code as the patch below. > What we intended to do with this change is to continue processing all > entry without breaking semantics. > > With the patch below our board seem to work fine again, but not sure > exactly why it takes so much time to check the list again. We are not > against the idea of the patch at all. We just want to ask you guys > how we should go to track this problem. it might be the slow usb? Could you try use debugfs and see if some queue and packet counters of mac80211/rt2x00 show excessive values? Have you been running the test with powersaving enabled or disabled? Ivo -- 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
