> Actually, I just looked at the specs again and the count value for mesh > is completely different. Instead of specifying the number of TBTTs > until the switch happens, it specifies the time in TUs until the switch > happens and 0 means at any time after the frame was sent (the same as > with nonmesh). In our implementation, we just decrease the count on > every beacon, which is wrong in the mesh case. Yes, you are absolutely correct. > > The count implementation for mesh is bogus. We need to fix that. > > What if, for now, I just fix the oops because of the rcu_derefence when > the rcu is not initialized Sure > and we fix the count implementation later? Hmm, even with unit of 100TU, we can't use the current count approach since the default TBTT for mesh is 1000 TU. ---- Chun-Yeow -- 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
