All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: linville@tuxdriver.com, johannes@sipsolutions.net,
	lrodriguez@atheros.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/3] ath9k: built-in rate control A-MPDU fix
Date: Sun, 10 Oct 2010 23:26:17 +0200	[thread overview]
Message-ID: <4CB22F79.60806@openwrt.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010102245220.31264@bigbill>

On 2010-10-10 10:51 PM, Björn Smedman wrote:
> This patch attempts to ensure that ath9k's built-in rate control algorithm 
> does not rely on the value of the ampdu_len and ampdu_ack_len tx status 
> fields unless the IEEE80211_TX_STAT_AMPDU flag is set.
> 
> This patch has not been tested.
> 
> Cc: <stable@kernel.org>
> Signed-off-by: Björn Smedman <bjorn.smedman@venatech.se>
> ---
> diff --git a/drivers/net/wireless/ath/ath9k/rc.c b/drivers/net/wireless/ath/ath9k/rc.c
> index ce1cd6d..13f9e88 100644
> --- a/drivers/net/wireless/ath/ath9k/rc.c
> +++ b/drivers/net/wireless/ath/ath9k/rc.c
> @@ -1375,6 +1375,12 @@ static void ath_tx_status(void *priv, struct ieee80211_supported_band *sband,
>  	if (tx_info->flags & IEEE80211_TX_STAT_TX_FILTERED)
>  		return;
>  
> +	if (!(tx_info->flags & IEEE80211_TX_STAT_AMPDU)) {
> +		tx_info->status.ampdu_ack_len =
> +			(tx_info->flags & IEEE80211_TX_STAT_ACK ? 1 : 0);
> +		tx_info->status.ampdu_len = 1;
> +	}
> +
Shouldn't mac80211 do this instead?

- Felix

  reply	other threads:[~2010-10-10 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10 20:51 [PATCH 3/3] ath9k: built-in rate control A-MPDU fix Björn Smedman
2010-10-10 21:26 ` Felix Fietkau [this message]
2010-10-10 21:44   ` Björn Smedman
2010-10-27 21:20     ` Luis R. Rodriguez

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=4CB22F79.60806@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=bjorn.smedman@venatech.se \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.