Hi,
I am doing some comparative tests, wanted to configure common
settings btw all STA's. wanted to limit agg_size to 24 in ath10k with
the below command.
echo "3 24" > /sys/kernel/debug/ieee80211/phy0/ath10k/htt_max_amsdu_ampdu
The ADDBA request still has 64 and when i run iperf it is aggregating 64 frames.
Except for 1 no number takes effect. If i configure 1 there is no ADDBA exchange
initiated by ath10k.
Is this expected? Can we control the aggregation size through driver?
latest wireless-drivers-next and linux-firmware git is used.
--
Thanks,
Regards,
Chaitanya T K.
What chipset, and what firmware version?
Thanks,
Ben
On 05/12/2017 07:43 AM, Krishna Chaitanya wrote:
> Hi,
>
> I am doing some comparative tests, wanted to configure common
> settings btw all STA's. wanted to limit agg_size to 24 in ath10k with
> the below command.
>
> echo "3 24" > /sys/kernel/debug/ieee80211/phy0/ath10k/htt_max_amsdu_ampdu
>
> The ADDBA request still has 64 and when i run iperf it is aggregating 64 frames.
>
> Except for 1 no number takes effect. If i configure 1 there is no ADDBA exchange
> initiated by ath10k.
>
> Is this expected? Can we control the aggregation size through driver?
>
> latest wireless-drivers-next and linux-firmware git is used.
>
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
On Mon, May 15, 2017 at 3:02 PM, Krishna Chaitanya
<[email protected]> wrote:
> On Fri, May 12, 2017 at 8:15 PM, Ben Greear <[email protected]> wrote:
>> What chipset, and what firmware version?
>>
>> Thanks,
>> Ben
>
> Hi Ben,
>
> I have missed your response. PFB details.
>
> chip: QCA986x/988x PCIe
> FW ver: 10.2.4.70.54 api 5
> kernel: 4.11.0-rc+7 (wireless-drivers-next)
>
Ben,
any clues?
>
>> On 05/12/2017 07:43 AM, Krishna Chaitanya wrote:
>>>
>>> Hi,
>>>
>>> I am doing some comparative tests, wanted to configure common
>>> settings btw all STA's. wanted to limit agg_size to 24 in ath10k with
>>> the below command.
>>>
>>> echo "3 24" > /sys/kernel/debug/ieee80211/phy0/ath10k/htt_max_amsdu_ampdu
>>>
>>> The ADDBA request still has 64 and when i run iperf it is aggregating 64
>>> frames.
>>>
>>> Except for 1 no number takes effect. If i configure 1 there is no ADDBA
>>> exchange
>>> initiated by ath10k.
>>>
>>> Is this expected? Can we control the aggregation size through driver?
>>>
>>> latest wireless-drivers-next and linux-firmware git is used.
>>>
>>
>> --
>> Ben Greear <[email protected]>
>> Candela Technologies Inc http://www.candelatech.com
On Fri, May 12, 2017 at 8:15 PM, Ben Greear <[email protected]> wrote:
> What chipset, and what firmware version?
>
> Thanks,
> Ben
Hi Ben,
I have missed your response. PFB details.
chip: QCA986x/988x PCIe
FW ver: 10.2.4.70.54 api 5
kernel: 4.11.0-rc+7 (wireless-drivers-next)
> On 05/12/2017 07:43 AM, Krishna Chaitanya wrote:
>>
>> Hi,
>>
>> I am doing some comparative tests, wanted to configure common
>> settings btw all STA's. wanted to limit agg_size to 24 in ath10k with
>> the below command.
>>
>> echo "3 24" > /sys/kernel/debug/ieee80211/phy0/ath10k/htt_max_amsdu_ampdu
>>
>> The ADDBA request still has 64 and when i run iperf it is aggregating 64
>> frames.
>>
>> Except for 1 no number takes effect. If i configure 1 there is no ADDBA
>> exchange
>> initiated by ath10k.
>>
>> Is this expected? Can we control the aggregation size through driver?
>>
>> latest wireless-drivers-next and linux-firmware git is used.
>>
>
> --
> Ben Greear <[email protected]>
> Candela Technologies Inc http://www.candelatech.com
--
Thanks,
Regards,
Chaitanya T K.
On Sun, May 21, 2017 at 8:36 PM, Ben Greear <[email protected]> wrote:
>
>
> On 05/20/2017 09:21 AM, Krishna Chaitanya wrote:
>>
>> On Mon, May 15, 2017 at 3:02 PM, Krishna Chaitanya
>> <[email protected]> wrote:
>>>
>>> On Fri, May 12, 2017 at 8:15 PM, Ben Greear <[email protected]>
>>> wrote:
>>>>
>>>> What chipset, and what firmware version?
>>>>
>>>> Thanks,
>>>> Ben
>>>
>>>
>>> Hi Ben,
>>>
>>> I have missed your response. PFB details.
>>>
>>> chip: QCA986x/988x PCIe
>>> FW ver: 10.2.4.70.54 api 5
>>> kernel: 4.11.0-rc+7 (wireless-drivers-next)
>>>
>> Ben,
>>
>> any clues?
>
>
> I haven't tried that test yet, and use a different
> firmware version. I did recently work on allowing larger
> AMSDU aggregates and have that working in my CT firmware and
> driver.
ok, so at least its suppose to work.
On 05/20/2017 09:21 AM, Krishna Chaitanya wrote:
> On Mon, May 15, 2017 at 3:02 PM, Krishna Chaitanya
> <[email protected]> wrote:
>> On Fri, May 12, 2017 at 8:15 PM, Ben Greear <[email protected]> wrote:
>>> What chipset, and what firmware version?
>>>
>>> Thanks,
>>> Ben
>>
>> Hi Ben,
>>
>> I have missed your response. PFB details.
>>
>> chip: QCA986x/988x PCIe
>> FW ver: 10.2.4.70.54 api 5
>> kernel: 4.11.0-rc+7 (wireless-drivers-next)
>>
> Ben,
>
> any clues?
I haven't tried that test yet, and use a different
firmware version. I did recently work on allowing larger
AMSDU aggregates and have that working in my CT firmware and
driver.
Thanks,
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com