On Wed, Mar 7, 2018 at 8:39 AM, Phani Siriki <[email protected]> wrote: > Hi Thomas > > Thank you for your reply. > > Could you please let me know how can I verify these queues on a mesh > router? (I am using TPLink router with Ath9k chipset).
try $ iw mesh0 mpath dump The mpath queue length is under the "QLEN" heading. > Also, the TXQ parameters can only be set if device is in AP or P2P > mode. Do you have any idea why this restriction is in place? I don't think there is any reason modifying the queue parameters wouldn't work in mesh mode. Why don't you hack up that code and give it a try. > https://github.com/torvalds/linux/blob/master/net/wireless/nl80211.c > > static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info) > { > > if (info->attrs[NL80211_ATTR_WIPHY_TXQ_PARAMS]) { > .... > if (netdev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP && > netdev->ieee80211_ptr->iftype != NL80211_IFTYPE_P2P_GO) > return -EINVAL; > ... > } > > Best Regards > Phani > > On Tue, Mar 6, 2018 at 11:59 PM, Thomas Pedersen <[email protected]> wrote: >> On Thu, Mar 1, 2018 at 7:27 AM, Phani Siriki <[email protected]> wrote: >>> Hi All >>> >>> I am trying to understand the queuing mechanism wireless mesh networks. >>> >>> As per AP mode is concerned, there are four queues (BK, BE, Vi, VO) >>> and traffic is controlled based on CWmin, CWmax, AIFS and TxOP. >>> >>> Does, mesh mode also involve these queues? Does mesh mode have any >>> queue or it is just a single queue? >> >> mesh mode maps to the different ACs like AP mode. The only additional >> queue in mesh is the mpath->frame_queue, which may be used if an >> active mpath for a given RA can't be found. >> >> -- >> thomas -- thomas
