From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>
Subject: Re: [PATCH v3] mac80211/drivers: rewrite the rate control API
Date: Mon, 20 Oct 2008 14:42:20 +0800 [thread overview]
Message-ID: <1224484940.24677.169.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1224052607.3027.20.camel@johannes.berg>
On Tue, 2008-10-14 at 23:36 -0700, Johannes Berg wrote:
> So after the previous changes we were still unhappy with how
> convoluted the API is and decided to make things simpler for
> everybody. This completely changes the rate control API, now
> taking into account 802.11n with MCS rates and more control,
> most drivers don't support that though.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
[...]
> @@ -318,9 +348,33 @@ static void iwl3945_rx_reply_tx(struct i
> }
>
> info = IEEE80211_SKB_CB(txq->txb[txq->q.read_ptr].skb[0]);
> - memset(&info->status, 0, sizeof(info->status));
> + ieee80211_tx_info_clear_status(info);
> +
> + /* Fill the MRR chain with some info about on-chip retransmissions */
> + rate_idx = iwl3945_hwrate_to_plcp_idx(tx_resp->rate);
> + if (info->band == IEEE80211_BAND_5GHZ)
> + rate_idx -= IWL_FIRST_OFDM_RATE;
> +
> + info->status.rates[0].count = tx_resp->failure_frame + 1;
This is useless. And it is even confusable with the later count++.
> + fail = tx_resp->failure_frame;
> + for(i = 0; i < 4; i++) {
Where does the '4' come from? Why not IEEE80211_TX_MAX_RATES?
> + int next = iwl3945_rs_next_rate(priv, rate_idx);
> +
> + info->status.rates[i].idx = rate_idx;
> +
> + if ((rate_idx == next) || (i == 3)) {
ditto
[...]
Other iwlwifi changes looks fine to me.
Thanks,
-yi
next prev parent reply other threads:[~2008-10-20 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:55 [PATCH] mac80211/drivers: rewrite the rate control API Johannes Berg
2008-10-15 6:36 ` [PATCH v3] " Johannes Berg
2008-10-20 6:42 ` Zhu Yi [this message]
2008-10-20 6:48 ` Johannes Berg
2008-10-20 7:06 ` Zhu Yi
2008-10-20 7:09 ` Johannes Berg
2008-10-20 8:04 ` Zhu Yi
2008-10-20 8:07 ` Johannes Berg
2008-10-21 4:07 ` Zhu Yi
2008-10-21 6:23 ` Zhu Yi
2008-10-21 6:43 ` Johannes Berg
2008-10-21 6:58 ` Zhu Yi
2008-10-21 10:40 ` [PATCH v4] " 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=1224484940.24677.169.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=vasanth@atheros.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;
as well as URLs for NNTP newsgroup(s).