From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] minstrel_ht: problems with HT40
Date: Thu, 09 May 2013 17:09:51 +0200 [thread overview]
Message-ID: <518BBC3F.2030007@rempel-privat.de> (raw)
In-Reply-To: <518BB57D.80204@openwrt.org>
Am 09.05.2013 16:41, schrieb Felix Fietkau:
> On 2013-05-09 3:42 PM, Oleksij Rempel wrote:
>> Hallo Felix,
>>
>> i found your patches for moving ath9k to minstrel_ht and decided to do
>> some testing.
>> For some reason, minstrel_ht exclude all HT40 rates in my network. With
>> native ath9k rate controller I'm able to use HT40.
>> Do you have any idea where to start digging?
> Do the rates not even show up in the debugfs rate control stats?
correct
> If so,
> check the value of sta->bandwidth at the time minstrel_ht_update_caps()
> is called.
hmm... for some reasons sta->bandwidth is always 0.
my rc_stats are in attachment
--
Regards,
Oleksij
-------------- next part --------------
type rate throughput ewma prob this prob retry this succ/attempt success attempts
CCK/LP 1.0M 0.9 99.9 100.0 0 0( 0) 29 30
CCK/SP 2.0M 0.0 0.0 0.0 0 0( 0) 0 0
CCK/SP 5.5M 0.0 0.0 0.0 0 0( 0) 0 0
CCK/SP 11.0M 0.0 0.0 0.0 0 0( 0) 0 0
HT20/LGI MCS0 6.2 100.0 100.0 1 0( 0) 1 1
HT20/LGI MCS1 11.7 100.0 100.0 0 0( 0) 1 1
HT20/LGI MCS2 16.4 100.0 100.0 0 0( 0) 1 1
HT20/LGI MCS3 20.7 100.0 100.0 0 0( 0) 1 1
HT20/LGI MCS4 28.0 100.0 100.0 5 0( 0) 1 1
HT20/LGI MCS5 27.9 82.9 100.0 5 0( 0) 15 19
HT20/LGI t MCS6 28.9 80.2 25.0 5 0( 0) 109 123
HT20/LGI T P MCS7 38.9 99.9 100.0 5 1( 1) 782 813
Total packet count:: ideal 975 lookaround 48
Average A-MPDU length: 1.0
next prev parent reply other threads:[~2013-05-09 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 13:42 [ath9k-devel] minstrel_ht: problems with HT40 Oleksij Rempel
2013-05-09 14:41 ` Felix Fietkau
2013-05-09 15:09 ` Oleksij Rempel [this message]
2013-05-09 15:16 ` Felix Fietkau
2013-05-09 17:02 ` Oleksij Rempel
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=518BBC3F.2030007@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.org \
/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.