From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Denton Gentry <denton.gentry@gmail.com>
Subject: Re: [RFC/RFT 2/2] ath10k: fix Rx aggregation reordering
Date: Fri, 27 Jun 2014 17:17:13 +0300 [thread overview]
Message-ID: <8761jmtp1y.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1403860015-31601-3-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 27 Jun 2014 11:06:55 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Firmware doesn't perform Rx reordering so it is
> left to the host driver to do that.
>
> Use mac80211 to perform reordering instead of
> re-inventing the wheel.
>
> This fixes TCP throughput issues in some
> environments (notably Windows stations connecting
> to ath10k AP).
>
> Reported-By: Denton Gentry <denton.gentry@gmail.com>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
[...]
> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c
> +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
> @@ -21,6 +21,7 @@
> #include "txrx.h"
> #include "debug.h"
> #include "trace.h"
> +#include "mac.h"
Why this? At least from a quick search I didn't see any reason to add this.
>
> #include <linux/log2.h>
>
> @@ -1533,10 +1534,95 @@ void ath10k_htt_t2h_msg_handler(struct ath10k *ar, struct sk_buff *skb)
> case HTT_T2H_MSG_TYPE_STATS_CONF:
> trace_ath10k_htt_stats(skb->data, skb->len);
> break;
> + case HTT_T2H_MSG_TYPE_RX_ADDBA: {
> + struct ath10k *ar = htt->ar;
> + struct htt_rx_addba *ev = &resp->rx_addba;
> + struct ath10k_peer *peer;
> + struct ath10k_vif *arvif;
> + u16 info0, tid, peer_id;
> +
> + info0 = __le32_to_cpu(ev->info0);
> + tid = MS(info0, HTT_RX_BA_INFO0_TID);
> + peer_id = MS(info0, HTT_RX_BA_INFO0_PEER_ID);
This event handling is pretty long. I think it would be better to have a
separate function for this event.
> + case HTT_T2H_MSG_TYPE_RX_DELBA: {
> + struct ath10k *ar = htt->ar;
> + struct htt_rx_addba *ev = &resp->rx_addba;
> + struct ath10k_peer *peer;
> + struct ath10k_vif *arvif;
> + u16 info0, tid, peer_id;
And the same for this event.
--
Kalle Valo
next prev parent reply other threads:[~2014-06-27 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 9:06 [RFC/RFT 0/2] mac80211/ath10k: fix Rx reordering Michal Kazior
2014-06-27 9:06 ` [RFC/RFT 1/2] mac80211: add support for Rx reordering offloading Michal Kazior
2014-07-08 7:10 ` Johannes Berg
2014-07-14 13:18 ` Michal Kazior
2014-06-27 9:06 ` [RFC/RFT 2/2] ath10k: fix Rx aggregation reordering Michal Kazior
2014-06-27 14:17 ` Kalle Valo [this message]
2014-06-30 5:41 ` Michal Kazior
2014-06-30 7:59 ` Kalle Valo
2014-06-27 18:17 ` [RFC/RFT 0/2] mac80211/ath10k: fix Rx reordering Denton Gentry
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=8761jmtp1y.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=denton.gentry@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).