From: "Jouni Malinen" <jkm@devicescape.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: James Ketrenos <jketreno@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Specifing rate control algorithm?
Date: Thu, 10 May 2007 08:48:59 -0700 [thread overview]
Message-ID: <20070510154859.GA24712@devicescape.com> (raw)
In-Reply-To: <20070510132756.2ca660a0@midnight.suse.cz>
On Thu, May 10, 2007 at 01:27:56PM +0200, Jiri Benc wrote:
> 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.
I don't think I would fully agree with this. Sure, the default rate
control algorithm should work with all drivers, but it is quite possible
that some rate control algorithms do not work with all drivers and some
combinations are much better than the "default algorithm". In other
words, I think there is benefit in drivers being able to "suggest" a
rate control algorithm to be used and there is not much point having to
force the user space to do this selection for the initial rate control
algorithm. Sure, this should still be something that can be changed from
user space, but the defaults selection could as well be the best
available combination.
Some hardware designs provide extra functionality that can be used to
improve rate control algorithm and as such, they may benefit greatly
from a specific rate control implementation. Because of this, there was
originally possibility for allowing the rate control algorithms to know
the driver name and use this to select whether to allow the algorithm to
be used with the driver. The request here was for a bit different way of
doing this, but anyway, I see value in this whichever way it would be
implemented.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-05-10 15:48 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
2007-05-10 15:48 ` Jouni Malinen [this message]
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=20070510154859.GA24712@devicescape.com \
--to=jkm@devicescape.com \
--cc=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 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).