On Tue, 2016-02-16 at 16:28 -0500, Avery Pennarun wrote: > Since around the beginning of time, ath9k aggregates have timed out > after > 5000 TU (around 5000ms) of inactivity, but nobody seems to be quite > sure > why, and this magic number seems to have migrated around from one > place to > another. An openbsd mailing list recently had a patch to disable the > timeout completely, which they say matches some commercial routers: > https://www.mail-archive.com/[email protected]/msg29456.html > > Even in Linux, several non-ath9k drivers default to no timeout > already. I > think changing it directly to zero would be safe, but to allow a more > structured investigation, let's make it configurable for now. > Since we just made it zero, perhaps we don't need this?
Although perhaps we still want it to be able to debug it? Anyway - you shouldn't create a debugfs file and play with the extern stuff etc., let minstrel create the debugfs file in minstrel_ht_alloc() johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
