From: Stefano Brivio <stefano.brivio@polimi.it>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
sam <sam@ravnborg.org>, Michael Wu <flamingice@sourmilk.net>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: [PATCH] mac80211: better rate control algorithm selection
Date: Fri, 21 Dec 2007 21:00:17 +0100 [thread overview]
Message-ID: <20071221210017.36f34fe3@morte> (raw)
In-Reply-To: <1198253375.16241.76.camel@johannes.berg>
On Fri, 21 Dec 2007 17:09:35 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:
> Below is the patch, comments welcome. I think this is the way we want
> it, tristate for all rate control algorithms regardless of whether
> mac80211 is modular (where =y then means "build algorithm into
> mac80211") and forcing one of the algorithms to y to do exactly that.
What about avoiding to force any algorithm to y, and instead always build a
dummy (a few lines of code which would just set the rate to the lowest
available) rate control algorithm into mac80211?
Looks good otherwise.
--
Ciao
Stefano
next prev parent reply other threads:[~2007-12-21 20:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 16:09 [PATCH] mac80211: better rate control algorithm selection Johannes Berg
2007-12-21 20:00 ` Stefano Brivio [this message]
2007-12-21 20:43 ` Johannes Berg
2007-12-21 20:57 ` Stefano Brivio
2007-12-21 21:15 ` Johannes Berg
2007-12-21 21:43 ` [PATCH v2] " Johannes Berg
2007-12-21 22:26 ` Stefano Brivio
2007-12-30 23:11 ` [PATCH] " Sam Ravnborg
2007-12-31 7:45 ` Christoph Hellwig
2008-01-02 8:41 ` Johannes Berg
2008-01-02 8:45 ` Christoph Hellwig
2008-01-02 8:52 ` Johannes Berg
2008-01-02 15:23 ` Michael Buesch
2008-01-02 15:27 ` Johannes Berg
2008-01-02 15:29 ` Michael Buesch
2008-01-02 23:05 ` Stefano Brivio
2008-01-02 14:04 ` Johannes Berg
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=20071221210017.36f34fe3@morte \
--to=stefano.brivio@polimi.it \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=sam@ravnborg.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).