From: Mattias Nissler <mattias.nissler@gmx.de>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC][PATCH] mac80211: Use PID controller for TX rate control
Date: Mon, 03 Dec 2007 12:59:04 +0100 [thread overview]
Message-ID: <1196683144.7470.14.camel@localhost> (raw)
In-Reply-To: <20071203125402.76562f26@morte>
On Mon, 2007-12-03 at 12:54 +0100, Stefano Brivio wrote:
> On Mon, 03 Dec 2007 12:03:00 +0100
> Mattias Nissler <mattias.nissler@gmx.de> wrote:
>
> > Wait a sec. Rate control is per station, so each AP will have it's own
> > rate control state.
>
> Ah, right. So fixing the related TODO may make sense.
What TODO excactly are you talking about?
>
> > Have you tried shorter sample intervals? Currently, it's once per
> > second. I plan to shorten it, maybe to 2Hz or even 4Hz and see whether
> > we can get better responsiveness and still stay stable. Also, the
> > integration time needs to be fine-tuned then.
>
> Well, the integration and control times are just fine. I mean, you can tune
> them, but I wouldn't expect the result to be very different. I just think we
> need some intervention when exceptional events occur. But if you decide to
> fix that TODO, considering association an exceptional event wouldn't make
> sense any longer. I've seen improvements after interpolation cycles too,
> though.
>
> > I also thought about your rate <-> failed frames table. I'm not
> > convinced this works, because I cannot see a way to obtain consistent
> > values for the table. Clearly, measuring table entries should be done
> > with equal interference conditions for all entries, and they must also
> > be adjusted over time. However, if we only collect data during normal
> > operation, we'll likely have good data only for the few recent rates we
> > were operating at.
>
> Yes, that's exactly what I meant.
So? How to do it right?
Mattias
next prev parent reply other threads:[~2007-12-03 11:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 19:05 [RFC][PATCH] mac80211: Use PID controller for TX rate control Mattias Nissler
2007-12-03 3:16 ` Stefano Brivio
2007-12-03 3:26 ` Stefano Brivio
2007-12-03 11:03 ` Mattias Nissler
2007-12-03 11:21 ` Tomas Winkler
2007-12-03 11:31 ` Mattias Nissler
2007-12-04 13:40 ` Johannes Berg
2007-12-04 17:45 ` Mattias Nissler
2007-12-05 10:16 ` Johannes Berg
2007-12-04 17:48 ` Stefano Brivio
2007-12-03 11:58 ` Stefano Brivio
2007-12-03 11:54 ` Stefano Brivio
2007-12-03 11:59 ` Mattias Nissler [this message]
2007-12-03 12:06 ` Stefano Brivio
2007-12-03 22:42 ` Nick Kossifidis
2007-12-03 23:36 ` Mattias Nissler
2007-12-04 1:41 ` Stefano Brivio
2007-12-04 8:15 ` Mattias Nissler
2007-12-04 10:01 ` Stefano Brivio
2007-12-04 17:40 ` Mattias Nissler
2007-12-04 17:57 ` Stefano Brivio
2007-12-04 18:33 ` Mattias Nissler
2007-12-04 18:40 ` Stefano Brivio
2007-12-04 20:50 ` Holger Schurig
2007-12-04 20:57 ` Mattias Nissler
2007-12-04 22:05 ` Nick Kossifidis
2007-12-05 7:49 ` Holger Schurig
2007-12-05 9:04 ` Mattias Nissler
2007-12-05 9:52 ` Stefano Brivio
2007-12-05 12:13 ` rc80211-pid: some tuning test results Stefano Brivio
2007-12-08 3:42 ` Stefano Brivio
2007-12-08 10:39 ` Mattias Nissler
2007-12-08 11:17 ` Stefano Brivio
2007-12-08 9:45 ` [RFC][PATCH] mac80211: Use PID controller for TX rate control Stefano Brivio
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=1196683144.7470.14.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stefano.brivio@polimi.it \
/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).