Re: [PATCH v2] ath10k: Increase AST table SKID length limit

SenthilKumar Jegadeesan sjega...@qti.qualcomm.com writes: The current SKID length configuration causes firmware to reject peer creation for not able to allocate AST entries for peers. This issue is observed when least significant 3 bytes are used ramdomly to create client MAC addresses.

RE: [PATCH v2] ath10k: Increase AST table SKID length limit

Jegadeesan, Senthil Cc: ath...@lists.infradead.org; linux-wireless@vger.kernel.org Subject: Re: [PATCH v2] ath10k: Increase AST table SKID length limit Have you tried testing this with 30+ stations associated and streaming data, and with other traffic on nearby channels (say, channel 1 and 6)? We see

Re: [PATCH v2] ath10k: Increase AST table SKID length limit

Have you tried testing this with 30+ stations associated and streaming data, and with other traffic on nearby channels (say, channel 1 and 6)? We see bad performance drop-off when we set number-of-peers above 100 (with CT firmware). My kernel will set AST skid limit to number-of-peers +

[PATCH v2] ath10k: Increase AST table SKID length limit

The current SKID length configuration causes firmware to reject peer creation for not able to allocate AST entries for peers. This issue is observed when least significant 3 bytes are used ramdomly to create client MAC addresses. AST table SKID length configuration is increased to maximum value