From: Stefano Brivio <stefano.brivio@polimi.it>
To: Mattias Nissler <mattias.nissler@gmx.de>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org,
Nick Kossifidis <mickflemm@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: rc80211-pid: some tuning test results
Date: Sat, 8 Dec 2007 12:17:25 +0100 [thread overview]
Message-ID: <20071208121725.58efae13@morte> (raw)
In-Reply-To: <1197110398.7472.17.camel@localhost>
On Sat, 08 Dec 2007 11:39:58 +0100
Mattias Nissler <mattias.nissler@gmx.de> wrote:
> Why wouldn't you let userspace set the raw parameters directly? The
> complicated scheme you propose prevents us to tell users/testers to
> "change the X parameter to see it gives better Y results". If you give
> access to the raw parameters, people can still tweak and tune them if
> the rate control fails for special situations (e.g. hardware that cannot
> report whether a frame was only retried or totally failed, special noise
> situations, whatever).
>
> Furthermore, you can still have the simplified scheme by providing a
> userspace tool (maybe even add it to iw, once we have an interface) that
> takes the input, calculates the raw parameters as below and writes the
> results to the kernel.
>
> Bottom line: This thing complicates the kernel, makes the thing less
> understandable for people who now what a PID controller is, complicates
> future tweaking and tuning of the (default) parameters and moreover
> could also be implemented in userspace. So my vote is against it.
I'm not so sure about this. I think that this is really specific to the
algorithm, so it looked like a natural choice to put this into the kernel.
But your points make a lot of sense. I should probably remove this from
here and send patches to iw.
> I've done a lot of code cleaning, maybe you want to base your patches on
> that. There's more to come, but I'll send them so you have something to
> start.
Me too I started to clean up the code, nevertheless if you send them it
will be useful. Thank you.
--
Ciao
Stefano
next prev parent reply other threads:[~2007-12-08 11:23 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
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 [this message]
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=20071208121725.58efae13@morte \
--to=stefano.brivio@polimi.it \
--cc=hs4233@mail.mn-solutions.de \
--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).