On Thu, Oct 20, 2011 at 10:51 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2011-10-20 at 10:41 -0700, Thomas Pedersen wrote: >> On Thu, Oct 20, 2011 at 4:16 AM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >> > On Wed, 2011-10-19 at 18:03 -0700, Thomas Pedersen wrote: >> >> Include the WMM IE in mesh peering and beacon frames. This is needed >> >> tell any potential peers what our WMM / EDCA parameters are. >> > >> > The goal seems fine but why bother building the WMM IE out of the actual >> > TX queue configuration? Shouldn't it normally be the other way around? >> > But I have no idea how QoS is supposed to work in a mesh... >> >> I'm not sure what you mean, this is the only way to get the WMM >> parameters? Usually these are just set with ieee80211_set_wmm_defaul() >> on bringing up the interface. > > Right, but > a) if you're using just the default, no need to derive from the default The user might wish to customize the queue parameters though. > b) should they be changeable? Why not? Thomas -- 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
