From: Ben Greear <greearb@candelatech.com>
To: 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 12:40:14 -0700 [thread overview]
Message-ID: <55b50a9a-49f4-d669-22d4-84e2efabf451@candelatech.com> (raw)
In-Reply-To: <ad97576c-d6dd-e29c-10d4-00b8aff77805@candelatech.com>
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
next prev parent reply other threads:[~2019-05-16 19:40 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 [this message]
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
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=55b50a9a-49f4-d669-22d4-84e2efabf451@candelatech.com \
--to=greearb@candelatech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.