From: Bob Copeland <me@bobcopeland.com>
To: "Thomas Hühn" <thomas@net.t-labs.tu-berlin.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
johannes.berg@intel.com, nbd@openwrt.org
Subject: Re: [PATCH 7/7] mac80211: improve minstrels rate sorting by means of throughput & probability
Date: Mon, 4 Mar 2013 10:02:19 -0500 [thread overview]
Message-ID: <20130304150219.GC14175@localhost> (raw)
In-Reply-To: <924BD93D-F69A-4D15-8E81-9720FC1B0E2B@net.t-labs.tu-berlin.de>
On Sat, Mar 02, 2013 at 12:01:59PM +0100, Thomas Hühn wrote:
> Hi Bob,
>
> I should have removed the debugging, thx for finding, I will fix this in v2.
Thanks!
> If I understand you right, your idea is to avoid equal rates for
> max_throughput and max_probability. The patch above would use equal
> rates for max_thr & max_prob. if the channel conditions allow this, so
> if they are pretty good. In other cases the max. probability rate can
> be totally different from max_thr. rate. So I do not understand the
> reasoning behind enforcing different rates for max_tp and max_prob.
> Minstrel will just apply its rule of max_prob_rate regardless if this
> rate also provides best or second best or other throughput values.
I guess my reasoning is that if you have an MRR setup like this:
mrr0 rate = 24, count = 8 (max_tp)
mrr1 rate = 18, count = 3 (max_tp2)
mrr2 rate = 24, count = 8 (max_prob)
mrr3 rate = 6, count = 3
...and you are located right next to the microwave that just got
turned on :) ... then that second set of 24 mbit retries may well be
quite some time of wasted airtime vs perhaps picking 12 mbit if the
probability of those rates is close.
[this was an actual table generated by minstrel from my simulation,
at least at the time, max retries was ignored by minstrel.]
> Would you mind to this this patch with your hwsim ?
That is a bit complicated :) To do so requires porting my userspace
wifi simulator to wmediumd, a process I have started but haven't
put much time into. Nevertheless it has been on my personal to-do for
quite some time, so I'll give it a go soon. I wouldn't hold up
acceptance of the patches for my testing though.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2013-03-04 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 17:37 [PATCH 0/7] mac80211: improve and consolidate minstrel rate control Thomas Huehn
2013-03-01 17:37 ` [PATCH 1/7] mac80211: merge EWMA calculation of minstrel_ht and minstrel Thomas Huehn
2013-03-01 17:37 ` [PATCH 2/7] mac80211: merge value scaling macros " Thomas Huehn
2013-03-01 17:37 ` [PATCH 3/7] mac80211: add documentation and verbose variable names in Thomas Huehn
2013-03-01 17:37 ` [PATCH 4/7] mac80211: extend minstrel's rate sampling to avoid unsampled rates Thomas Huehn
2013-03-01 17:37 ` [PATCH 5/7] mac80211: add lowest rate into minstrel's randmon rate sampling table Thomas Huehn
2013-03-01 17:37 ` [PATCH 6/7] mac80211: treat minstrel success probabilities below 10% as implausible Thomas Huehn
2013-03-01 17:37 ` [PATCH 7/7] mac80211: improve minstrels rate sorting by means of throughput & probability Thomas Huehn
2013-03-01 18:41 ` Bob Copeland
2013-03-02 11:01 ` Thomas Hühn
2013-03-04 15:02 ` Bob Copeland [this message]
2013-03-01 18:45 ` [PATCH 0/7] mac80211: improve and consolidate minstrel rate control Johannes Berg
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=20130304150219.GC14175@localhost \
--to=me@bobcopeland.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
--cc=thomas@net.t-labs.tu-berlin.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 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).