From: Mattias Nissler <mattias.nissler@gmx.de>
To: Stefano Brivio <stefano.brivio@polimi.it>
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, 04 Dec 2007 09:15:03 +0100 [thread overview]
Message-ID: <1196756103.7476.12.camel@localhost> (raw)
In-Reply-To: <20071204024146.15689ee3@morte>
Hi Stefano,
On Tue, 2007-12-04 at 02:41 +0100, Stefano Brivio wrote:
> I would say that these results show that the derivative coefficient is too
> high, or that the sharpening factor I introduced doesn't work that good.
> Anyway, just by a lowering a bit the failed frames target, results should be
> far better than the plain -simple algorithm.
Um, if Nick says the device has problems transmitting frames, IMHO this
will make it quite impossible to get the PID rate control right by
tuning parameters. Of course you can set the failed frames percentage
target to 100, but that's certainly not what we want. While I'm at it,
we should really run tests with different target values to see what
target gives us the best throughput in noisy situations.
Just an idea for your hack: wouldn't it be easier if we had all these
parameters accessible via debugfs instead of module parameters? Also, it
might be useful to have the parameters in sysfs so they can be changed
also for production systems, once mac80211 is stable.
Having the parameters in debugfs would also make things much easier for
me, since mac80211 oopses on module unload every now and then. I think
that started with the 2.6.24 series. So far I haven't had the time to
figure out why.
Mattias
next prev parent reply other threads:[~2007-12-04 8:15 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 [this message]
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=1196756103.7476.12.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.