From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thomas Pedersen <thomas@cozybit.com>,
linux-wireless@vger.kernel.org, Sandesh Goel <sgoel@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>
Subject: Re: [PATCH 2/2] mwl8k: Tell mac80211 we have rate adaptation in AP FW
Date: Mon, 14 Feb 2011 11:57:36 +0100 [thread overview]
Message-ID: <20110214105736.GA1727@mail.wantstofly.org> (raw)
In-Reply-To: <1297678711.3785.18.camel@jlt3.sipsolutions.net>
On Mon, Feb 14, 2011 at 11:18:31AM +0100, Johannes Berg wrote:
> > > /* Set rssi values to dBm */
> > > hw->flags |= IEEE80211_HW_SIGNAL_DBM;
> > > + /* AP FW has rate control */
> > > + if (priv->ap_fw)
> > > + hw->flags |= IEEE80211_HW_HAS_RATE_CONTROL;
> > > hw->vif_data_size = sizeof(struct mwl8k_vif);
> > > hw->sta_data_size = sizeof(struct mwl8k_sta);
> >
> > I got this same patch (almost exactly the same -- STA firmware actually
> > also has rate control so the added AP check in this version of the patch
> > is bogus) sent to me a number of times now, the last time from Pradeep
> > Nemavat <pnemavat@marvell.com> in private email on Feb 26 2010. This
> > is what I wrote back to him at the time:
> >
> > | mac80211.h says:
> > |
> > | * @IEEE80211_HW_HAS_RATE_CONTROL:
> > | * The hardware or firmware includes rate control, and cannot be
> > | * controlled by the stack. As such, no rate control algorithm
> > | * should be instantiated, and the TX rate reported to userspace
> > | * will be taken from the TX status instead of the rate control
> > | * algorithm.
> > | * Note that this requires that the driver implement a number of
> > | * callbacks so it has the correct information, it needs to have
> > | * the @set_rts_threshold callback and must look at the BSS config
> > | * @use_cts_prot for G/N protection, @use_short_slot for slot
> > | * timing in 2.4 GHz and @use_short_preamble for preambles for
> > | * CCK frames.
> > |
> > | In particular, the "need to report TX rate used in the TX status"
> > | requirement is something that we don't do, which is why I didn't merge
> > | the IEEE80211_HW_HAS_RATE_CONTROL change upstream yet. (I know that
> > | it improves performance, but performance is secondary to correctness.)
>
> Well, this objection is bogus. If you ask for minstrel rate control, and
> then don't use what it does, then not only will it perform less well and
> minstrel will converge to some arbitrary value, it will also mean that
> the rate reported to userspace (say in tcpdump) is *WRONG*. That's even
> worse than not reporting it.
Well, OK, but after this patch, it will still report bogus rates to
userspace (at least it did when I last tried it). If we're addressing
this anyway, let's fix that properly.
thanks,
Lennert
prev parent reply other threads:[~2011-02-14 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 0:03 [PATCH 1/2] mwl8k: fix rf_antenna rx argument for AP Thomas Pedersen
2011-02-12 0:03 ` [PATCH 2/2] mwl8k: Tell mac80211 we have rate adaptation in AP FW Thomas Pedersen
2011-02-12 0:34 ` Lennert Buytenhek
2011-02-12 1:03 ` Thomas Pedersen
2011-02-14 10:18 ` Johannes Berg
2011-02-14 10:57 ` Lennert Buytenhek [this message]
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=20110214105736.GA1727@mail.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=sgoel@marvell.com \
--cc=thomas@cozybit.com \
/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