Hi Thomas
I am able to see the correct values after I enable the wifi interface
and with the following changes.
Index: compat-wireless-2015-03-09/drivers/net/wireless/ath/ath9k/debug.c
===
--- compat-wireless-2015-03-09.orig/drivers/
Hi Thomas
I modified the code and tried to set the TXQ parameters for mesh
interface. I didn't observe any error.
However, I modified the ath9k driver code to verify default TXQ
parameters. But I am observing same values for all the queues and the
cwmin is looks different.
To my understanding, t
Thanks Thomas. I will try to hack the code and let you know.
Best Regards
Phani
On Thu, Mar 15, 2018 at 5:31 PM, Thomas Pedersen wrote:
> On Wed, Mar 7, 2018 at 8:39 AM, Phani Siriki wrote:
>> Hi Thomas
>>
>> Thank you for your reply.
>>
>> Could you please let me know how can I verify these qu
On Wed, Mar 7, 2018 at 8:39 AM, Phani Siriki 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" he
Could someone help me on this?
On Wed, Mar 7, 2018 at 10:39 AM, Phani Siriki 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).
>
> Also, the TXQ parameters can only be
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).
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?
https:/
On Thu, Mar 1, 2018 at 7:27 AM, Phani Siriki 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 als
