linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: Mattias Nissler <mattias.nissler@gmx.de>
Cc: Nick Kossifidis <mickflemm@gmail.com>,
	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: Tue, 4 Dec 2007 18:57:19 +0100	[thread overview]
Message-ID: <20071204185719.2eba303c@morte> (raw)
In-Reply-To: <1196790047.7472.5.camel@localhost>

On Tue, 04 Dec 2007 18:40:47 +0100
Mattias Nissler <mattias.nissler@gmx.de> wrote:

> I don't think this data is useful for tuning the TX control algorithm at
> all. In the case of a noisy channel, you can improve the rate of
> successful transmission by switching to a more-robust rate. However, if
> the driver just gets the parameters wrong, a slower rate won't help at
> all, thus the feedback loop model on which the PID controller relies is
> severely flawed.

Well, I may object that here it looks like that setting a lower rate
actually yields a lower failed frames ratio. But I agree with you, this
data is suboptimal - at the very least - for helping us with tuning.

> Ah, ok, module parameters show up in sysfs. This is good for testing,
> but if we want to make some parameters available for everybody, we
> cannot rely on module parameters, i.e. when mac80211 is compiled int the
> kernel. I'd say we even want to be able to tweak the parameters on a per
> device basis, we should really add them to mac80211 sysfs.

Please see Johannes's proposal [1]. I tend to agree with that. Here comes
my plan: for testing, I'd say we can stick to those modparams I introduced
last night, setting perms to 644 and just being careful to bring down the
interface before changing them through sysfs. When we're done with testing,
we can decide which parameters need to be exported and which don't, and
then implement proper locking and exporting parameters through nl80211. Is
this OK for you?


[1] Message-Id: <1196775624.6060.52.camel@johannes.berg>, on linux-wireless.


--
Ciao
Stefano

  reply	other threads:[~2007-12-04 18:01 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
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 [this message]
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=20071204185719.2eba303c@morte \
    --to=stefano.brivio@polimi.it \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mattias.nissler@gmx.de \
    --cc=mickflemm@gmail.com \
    /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).