From: Jiri Benc <jbenc@suse.cz>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Specifing rate control algorithm?
Date: Thu, 10 May 2007 13:27:56 +0200 [thread overview]
Message-ID: <20070510132756.2ca660a0@midnight.suse.cz> (raw)
In-Reply-To: <464253CE.2030504@linux.intel.com>
On Wed, 09 May 2007 16:05:50 -0700 James Ketrenos wrote:
> ieee80211_init_rate_ctrl_alg is the only function that can select the
> rate control algorithm by name, and that symbol is not set as
> EXPORT_SYMBOL.
That's true and it's not going to be exported.
> Currently the stack picks the first one it finds and I can't find a way
> for the driver or the user to override this behavior (esp. if the rate
> control algorithm is compiled as a built-in)
It was possible to change the rate control algorithm through sysfs,
unfortunately this ability was removed during the conversion to
debugfs. It will be made possible again through nl80211.
> Adding EXPORT_SYMBOL for ieee80211_init_rate_ctrl_alg would allow the
> driver to request the algorithm known to work best with that hardware.
A driver is not supposed to set rate control. Under no circumstances.
If you know about a bug in default rate control algorithm, fix it and
send a patch. Otherwise, fix your driver.
> we can change ieee80211_register_hw() to take a 'name' parameter
> specifying the rate control algorithm to use. Drivers that don't care
> can pass NULL and the stack will do what it does now (pick the first
> algorithm registered with the stack)
NACK.
> Preference?
Write a patch for nl80211/cfg80211.
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-05-10 11:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:05 Specifing rate control algorithm? James Ketrenos
2007-05-10 11:27 ` Jiri Benc [this message]
2007-05-10 15:48 ` Jouni Malinen
2007-05-10 16:00 ` Tomas Winkler
2007-05-10 16:17 ` James Ketrenos
2007-05-10 17:11 ` Johannes Berg
2007-05-10 17:26 ` Jouni Malinen
2007-05-10 19:36 ` jketreno
2007-05-11 11:36 ` Johannes Berg
2007-05-10 17:42 ` Jiri Benc
2007-05-10 20:17 ` jketreno
2007-05-10 19:23 ` Jiri Benc
2007-05-10 22:24 ` Tomas Winkler
2007-05-11 0:12 ` John W. Linville
2007-05-11 8:09 ` Andy Green
2007-05-11 9:07 ` Jeff Garzik
2007-05-11 9:36 ` Andy Green
2007-05-11 14:23 ` Jouni Malinen
2007-05-11 15:04 ` Andy Green
2007-05-11 15:42 ` Jouni Malinen
2007-05-11 10:21 ` Jiri Benc
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=20070510132756.2ca660a0@midnight.suse.cz \
--to=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
/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.