From: Mattias Nissler <mattias.nissler@gmx.de>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Exponential moving average estimate for rc80211_simple
Date: Sun, 25 Nov 2007 19:25:26 +0100 [thread overview]
Message-ID: <1196015126.8365.14.camel@localhost> (raw)
In-Reply-To: <1196014318.8365.1.camel@localhost>
Hi,
I guess this patch will spawn a discussion, so let me comment a little
more.
I have a rt61pci card sitting in the box under my desk. Seems reception
isn't really good below my desk :-) With the current rc80211_simple I
have the following behaviour: Failed frames accumulate until
rc80211_simple decides to lower the rate. Unfortunately, the rate
control algorithm is quite unresponsive, so my rate goes down to 1Mb/s
immediately. Then I have to wait for some minutes until the statistics
have recovered enough for the rate control to raise the rate. Of course
it goes straight through the roof to 54Mb/s. Errors accumulate, and soon
I'm back at 1Mb/s. And so on.
My patch changes the way the average of failed frames is computed. By
using a moving average approach, old values don't influence the estimate
after some time (note the current approach always uses the plain
counters, thus using all information accumulated since the interface has
been brought up!). This makes the estimate more responsive and thus the
rate control algorithm works a lot better.
I've tested my approach by listening to web radio for some time and it
successfully keeps me between around 24Mb/s and 54Mb/s. From what I see
here, that's a big improvement over the roller coaster rate control
behaviour I had before.
Mattias
prev parent reply other threads:[~2007-11-25 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 18:11 [PATCH] mac80211: Exponential moving average estimate for rc80211_simple Mattias Nissler
2007-11-25 18:25 ` Mattias Nissler [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=1196015126.8365.14.camel@localhost \
--to=mattias.nissler@gmx.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).