linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.intel.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Specifing rate control algorithm?
Date: Wed, 09 May 2007 16:05:50 -0700	[thread overview]
Message-ID: <464253CE.2030504@linux.intel.com> (raw)


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.

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)

Adding EXPORT_SYMBOL for ieee80211_init_rate_ctrl_alg would allow the driver to request the algorithm known to work best with that hardware. 

-or- 

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)

Preference?

James

             reply	other threads:[~2007-05-09 23:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 23:05 James Ketrenos [this message]
2007-05-10 11:27 ` Specifing rate control algorithm? Jiri Benc
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=464253CE.2030504@linux.intel.com \
    --to=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 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).