From: Mattias Nissler <mattias.nissler@gmx.de>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Stefano Brivio <stefano.brivio@polimi.it>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: [RFC][PATCH 0/4] mac80211: rate control rework
Date: Sat, 08 Dec 2007 12:21:46 +0100 [thread overview]
Message-ID: <1197112906.7472.48.camel@localhost> (raw)
This patch set does some general maintenance at the rate control front,
adds the PID algorithm, makes it the default and removes the old simple
algorihtm. Note that it is WIP, I'm sending it to get comments and to
sync my PID work with Stefano.
Other things I plan to do but not yet in the patches are:
* Change the get_rate() interface to remove the local pointer (can be
obtained from the netdev)
* track wich packets actually use a rate assigned by the rate control
(maybe add a flag to tx control) and only pass them pack to the rate
control for evaluation. Or at least give the rate control tx_status()
the information whether the frame was sent with a rate obtained from the
rate control algo.
Mattias
reply other threads:[~2007-12-08 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1197112906.7472.48.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).