From: Max Sav <testX@hotmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k rate control locked to the minimum required tx rate
Date: Fri, 15 Apr 2016 11:28:14 +0000 [thread overview]
Message-ID: <DB5PR08MB0853F29784F1401733C33B43A1680@DB5PR08MB0853.eurprd08.prod.outlook.com> (raw)
Hello,
I'm using the old ath9k rate control on a kernel 3.14.65 over a NOHT 802.11a channel.
I'm enforcing the usable bitrate through the iw command:
iw dev wlan0 set bitrates legacy-5 12 18 24 36 48 54
I found that as soon as the radio channel becomes poor the rate control scale the rate correctly but when it reaches the minimum rate it stay locked to the minimum bitrate (12 Mbits/s).
At the same time "iw wlan0 station dump" report a different TX rate (9 Mbit/s in place of 12 Mbit/s).
Is this something that was already seen before?
Regards,
Max
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160415/4763b141/attachment.htm
reply other threads:[~2016-04-15 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DB5PR08MB0853F29784F1401733C33B43A1680@DB5PR08MB0853.eurprd08.prod.outlook.com \
--to=testx@hotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).