From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] why is bitrate of 65.0 MBit/s MCS 7 appropriate for signal strength of -93 dBm?
Date: Wed, 06 Apr 2011 16:31:37 +0200 [thread overview]
Message-ID: <4D9C7949.1050307@openwrt.org> (raw)
In-Reply-To: <BANLkTikaGBzn-WrRqgRXoU0He47bdH9r8w@mail.gmail.com>
On 2011-04-06 4:17 PM, Larry Vaden wrote:
> On Wed, Apr 6, 2011 at 5:26 AM, Mohammed Shafi<shafi.ath9k@gmail.com> wrote:
>> On Wed, Apr 6, 2011 at 3:28 PM, Larry Vaden<vaden@texoma.net> wrote:
>>> Mindful that we are all ignorant, just about different things, I ask
>>> the ? in the subject line.
>>>
>>> Would that not influence the success ratio and the performance?
>>
>> ath9k rate control is based on PER(packet error rate), but previously
>> it is based on RSSI.
>> But i doubt you are using minstrel rate control, for that please read
>> http://wireless.kernel.org/en/developers/Documentation/mac80211/RateControl/minstrel
>
> With all due respect, I do not think your answer is responsive to the
> question and the data presented.
>
>>> tx packets: 45
>>> tx retries: 308
>>> tx failed: 23
>
> Note a FAILURE RATE of 50% and retries ~ 700%.
Simple packet/retry/fail counters are completely misleading when it
comes to debugging wireless issues.
> So, why is 65.0 MBit/s MCS 7 even on the table if rate control is based on PER?
Because the assumption that lower rates always work better than higher
rates is a bad one to make in a rate control algorithm.
> Is it possible that some code other than ath9k is jacking with the
> data rates (read: I am ignorant about what protections OpenWrt might
> have)?
You can find better statistics with much more meaningful output in
/sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/rc_stats
- Felix
next prev parent reply other threads:[~2011-04-06 14:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 9:58 [ath9k-devel] why is bitrate of 65.0 MBit/s MCS 7 appropriate for signal strength of -93 dBm? Larry Vaden
2011-04-06 10:26 ` Mohammed Shafi
2011-04-06 14:17 ` Larry Vaden
2011-04-06 14:31 ` Felix Fietkau [this message]
2011-04-06 14:49 ` Larry Vaden
2011-04-06 14:52 ` Felix Fietkau
2011-04-06 14:53 ` Larry Vaden
2011-04-06 23:33 ` Larry Vaden
2011-04-07 7:36 ` Mohammed Shafi
2011-04-07 7:37 ` Mohammed Shafi
2011-04-07 12:29 ` Larry Vaden
2011-04-07 15:33 ` Daniel Halperin
2011-04-07 16:29 ` Larry Vaden
2011-04-08 0:22 ` Adrian Chadd
2011-04-08 0:33 ` Larry Vaden
2011-04-08 0:35 ` Larry Vaden
2011-04-08 0:41 ` Adrian Chadd
2011-04-08 1:03 ` Larry Vaden
2011-04-06 14:48 ` Mohammed Shafi
2011-04-06 14:51 ` Larry Vaden
2011-04-06 14:59 ` Mohammed Shafi
2011-04-06 15:18 ` Larry Vaden
2011-04-06 16:02 ` Mohammed Shafi
2011-04-06 16:08 ` Daniel Halperin
2011-04-06 16:24 ` Larry Vaden
2011-04-07 22:25 ` Larry Vaden
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=4D9C7949.1050307@openwrt.org \
--to=nbd@openwrt.org \
--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.