linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Minstrel's definition of best throughput
Date: Thu, 20 Aug 2009 22:45:40 +0200	[thread overview]
Message-ID: <4A8DB5F4.8060809@openwrt.org> (raw)
In-Reply-To: <4A8D5A48.5070809@nets.rwth-aachen.de>

Arnd Hannemann wrote:
> Hi,
> 
> while watching the rc_stats of minstrel, I noticed
> that minstrel does not choose the rate with best throughput.
> For example, I often see something like this:
> 
> rate     throughput  ewma prob   this prob  this succ/attempt   success    attempts
>      1         0.8       89.1      100.0          0(  0)       1490        2257
>      2         1.8       95.3      100.0          0(  0)         13          15
>      5.5       4.8       95.5      100.0          0(  0)         17          22
>   P 11         9.4       98.5      100.0          0(  0)       1532        2195
>      6         5.4       95.6      100.0          0(  0)         28          88
>      9         8.1       96.2      100.0          0(  0)        143         431
>     12         8.7       78.8      100.0          0(  0)        209         814
>     18        12.3       75.8      100.0          0(  0)        302        2416
>     24        18.3       86.2      100.0          0(  0)       5765        9196
>     36         2.6       85.2      100.0          0(  0)     736813      886517
> T   48        14.7       97.4      100.0          2(  2)    3433862     4411674
>  t  54         8.5       73.3      100.0          0(  0)    1488241     2180261
> 
> 
> Why did minstrel chose the 48M rate, and not 24M for the best throughput rate?
The table looks weird. Maybe there's a race between the update of the
table and the display through debugfs. Either way, 48M is definitely the
best throughput rate based on the ewma prob, but the calculated
throughput value looks a bit off.

> Also "this prob" seems fishy to me, its always 100...
"this prob" refers to the current interval, not the value after EWMA, so
it's always calculated from this succ/attempt and 100.0 makes sense here.

> Another thing: I noticed that the througput field in minstrel_rate is never used?
> Should I send a patch, removing it? Or does anyone remember why it was there
> in the first place?
I think you can remove it. I think initially I planned on calculating
both the EWMA throughput and the one from the measurement interval, but
didn't do that, because it's not displayed anywhere and would serve no
other purpose.

- Felix

      reply	other threads:[~2009-08-20 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 14:14 Minstrel's definition of best throughput Arnd Hannemann
2009-08-20 20:45 ` Felix Fietkau [this message]

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=4A8DB5F4.8060809@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=hannemann@nets.rwth-aachen.de \
    --cc=linux-wireless@vger.kernel.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 NNTP newsgroup(s).