From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Sebastian Gottschall <s.gottschall@newmedia-net.de>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: Problem with 9984 in routed mode with 512b frames.
Date: Thu, 16 May 2019 13:20:18 -0700 [thread overview]
Message-ID: <958466d1-2d3a-d1cd-e1f6-65e032f15e15@candelatech.com> (raw)
In-Reply-To: <CAJ-VmokYa4LpQCokRu_7gp1LsV+-1fS=UmWd=6SZ07F-O5cw+w@mail.gmail.com>
On 5/16/19 1:16 PM, Adrian Chadd wrote:
> You can't do AMPDU with OFDM/CCK. If they're setting the AMPDU bit
> then that's wrong. it needs to be individual MPDU/PPDUs.
>
> There's a benefit for CCK. OFDM 6M is I think roughly the same as OFDM
> MCS0. But CCK is a lot more reliable.
5Ghz can (should) not do CCK anyway. Do you have any reference for why
you think CCK will be better? The one I found shows otherwise:
https://d2cpnw0u24fjm4.cloudfront.net/wp-content/uploads/LaminatedCard_RevolutionWiFiMCStoSNRSinglePage.png
Thanks,
Ben
>
>
> -adrian
>
> On Thu, 16 May 2019 at 13:10, Ben Greear <greearb@candelatech.com> wrote:
>>
>> On 5/16/19 12:55 PM, Adrian Chadd wrote:
>>> You can totally go down to OFDM yeah but you then need to send it at
>>> 20MHz and non-AMPDU.
>>>
>>> Is it maybe the retry code + rate control code is retagging an AMPDU
>>> at a lower rate and it's transitioning down to CCK/OFDM without
>>> breaking the AMPDU apart?
>>
>> It was sending a one-frame AMPDU, and one frame AMSDU for that matter. Maybe
>> there is some bit in the tx descriptor that needed to be twiddled as well
>> to make OFDM able to work, but I don't know what that would be.
>>
>> Is there any advantage of (any) OFDM over MCS0 HT 20Mhz as far as range or
>> SNR goes? The chart I found made it look like there was not, and if
>> not, then why bother at all with OFDM if peer advertises HT/VHT rates?
>>
>> Thanks,
>> Ben
>>
>>>
>>>
>>> -a
>>>
>>> On Thu, 16 May 2019 at 12:40, Ben Greear <greearb@candelatech.com> wrote:
>>>>
>>>> On 5/15/19 6:00 AM, Ben Greear wrote:
>>>>> On 5/15/19 5:26 AM, Sebastian Gottschall wrote:
>>>>>>
>>>>>> Am 15.05.2019 um 14:20 schrieb Ben Greear:
>>>>>>> On 05/14/2019 09:26 PM, Sebastian Gottschall wrote:
>>>>>>>> can you send me a detailed instruction for testing this on my devices? so which commands have been used for generating the traffic etc. (iperf3?)
>>>>>>>
>>>>>>> I am using our own traffic generator, but I imagine iperf3 should work fine too.
>>>>>>>
>>>>>>> I am testing on x86-64 and so forth. Maybe you can test with UDP small-packet load on your platform
>>>>>>> in routed mode (ie, external iperf generator through your AP) and see if you see issues?
>>>>>> thats the plan. can you do a test with iperf3 to see if its reproduceable. i mean i will test it on ipq based boards and x64. but to make sure that the scenario
>>>>>> is identical which raised up your issue, it would be find if we have identical software for testing including the same options
>>>>
>>>> I think I found the issue. The rate-ctrl logic in the firmware allows a transition from HT/VHT 20 MCS0 down to OFDM rates.
>>>> It seems the hardware does not like to see an AMPDU with an OFDM rate for 20Mhz and a VHT rate for 80Mhz (or maybe just the
>>>> single OFDM rate is the fault).
>>>>
>>>> If you can edit firmware, then setting this to 0 probably fixes the issue.
>>>>
>>>> g_rc_cck_rate_allowed
>>>>
>>>> I think to reproduce you'd need to send high speed traffic in a situation where the
>>>> RF environment is going to make rate-ctrl fail quite a bit. (Slow speed should
>>>> work too, but it would likely take a lot longer).
>>>>
>>>> And, it is always possible that whatever I saw when testing mostly-stock FW is different
>>>> from what I eventually debugged to in my firmware. Still, from looking at MCS vs SNR
>>>> charts, there seems to be no advantage to trying OFDM vs MCS0 for 20Mhz.
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>> --
>>>> Ben Greear <greearb@candelatech.com>
>>>> Candela Technologies Inc http://www.candelatech.com
>>>>
>>>>
>>>> _______________________________________________
>>>> ath10k mailing list
>>>> ath10k@lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>>
>>
>>
>> --
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc http://www.candelatech.com
>>
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-05-16 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 1:52 Problem with 9984 in routed mode with 512b frames Ben Greear
2019-05-15 4:26 ` Sebastian Gottschall
2019-05-15 12:20 ` Ben Greear
2019-05-15 12:26 ` Sebastian Gottschall
2019-05-15 13:00 ` Ben Greear
2019-05-16 19:40 ` Ben Greear
2019-05-16 19:55 ` Adrian Chadd
2019-05-16 20:09 ` Ben Greear
2019-05-16 20:16 ` Adrian Chadd
2019-05-16 20:20 ` Ben Greear [this message]
2019-05-16 20:35 ` Adrian Chadd
2019-05-17 4:21 ` Sebastian Gottschall
2019-05-17 11:48 ` Ben Greear
2019-05-17 15:05 ` Sebastian Gottschall
2019-05-17 15:47 ` Adrian Chadd
2019-05-17 16:00 ` Ben Greear
2019-05-17 16:12 ` Adrian Chadd
2019-05-20 16:59 ` Sebastian Gottschall
2019-05-20 19:25 ` Adrian Chadd
2019-05-20 19:54 ` Ben Greear
2019-05-20 16:58 ` Sebastian Gottschall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=958466d1-2d3a-d1cd-e1f6-65e032f15e15@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@newmedia-net.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox