On Sun, 2011-02-13 at 09:56 -0800, Nathaniel J. Smith wrote: > Previously, the iwlwifi driver filled its transmit queue until it > reached a high-water mark, and then stopped until it had fallen to a > low-water mark. This basic logic makes sense for interrupt mitigation > -- you might not want to wake up the CPU after every packet, but > instead wait until a batch of packets has been sent -- except the > iwlwifi driver doesn't actually do any interrupt mitigation; the CPU > wakes up after every packet transmitted anyway. So we simplify the > code to maintain only a single limit on total queue length, and > whenever we drop below that limit we allow more packets in. > > This patch should have no user-visible effect. I'm pretty sure the devices (but maybe not 3945) implement interrupt mitigation at least in some cases. How did you arrive at the conclusion that "the driver doesn't actually do any interrupt mitigation"? johannes -- 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
