On 11 December 2015 at 09:19, Kalle Valo <kv...@codeaurora.org> wrote: > Janusz Dziedzic <janusz.dzied...@tieto.com> writes: > >> In case of MCC we can setup STA/AP(GO) ratio. >> Eg. setting sta_ap_ratio=80 >> STA will get 80% of time, while AP(GO) 20%. >> Setup correct ctwindow. >> >> Signed-off-by: Janusz Dziedzic <janusz.dzied...@tieto.com> > > Why? What's the use case? > By default beacon_int/2 is used in current implementation. This patch was developed as a proof of concept in case we would like to use MCC and need change this 50/50. Eg, for some reason we need higher BW/ more air time for STA or AP - depends on case. For my case STA connection to Gateway was more important that clients connected to an AP - so just used 70/30.
> And isn't there a better way to do this? Like using nl80211 (via > wpasupplicant?) or debugfs? > I wasn't sure here, but maybe some prio param on the VIF could be used here? Eg. VIF1 - prio 50 VIF2 - prio 100 VIF1_time = 50 / (50 + 100) = 33% VIF2_time = 100 / (50 + 100) = 66% with some default prio eg. 100. But for sure this is more work, and I am not sure someone else will need this? BR Janusz > -- > Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
