From: Felix Fietkau <nbd@openwrt.org>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath9k: Send legacy rated frames as unaggregated
Date: Mon, 22 Aug 2011 17:02:16 +0200 [thread overview]
Message-ID: <4E526F78.1030302@openwrt.org> (raw)
In-Reply-To: <1314016632-1742-1-git-send-email-rmanohar@qca.qualcomm.com>
On 2011-08-22 2:37 PM, Rajkumar Manoharan wrote:
> Currently the aggregation is formed till the aggregation limit
> is reached and the rate lookup is done for the first frame alone.
> But there can be a legacy rated frames in tid queue. This patch
> limits the subframe addition based on last MRR's rate and sends
> the legacy rated frames as unaggregated one.
>
> Signed-off-by: Rajkumar Manoharan<rmanohar@qca.qualcomm.com>
> ---
> drivers/net/wireless/ath/ath9k/xmit.c | 23 ++++++++++++++++++++++-
> 1 files changed, 22 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c
> index 2062672..41d9184 100644
> --- a/drivers/net/wireless/ath/ath9k/xmit.c
> +++ b/drivers/net/wireless/ath/ath9k/xmit.c
> @@ -571,6 +571,26 @@ static void ath_tx_complete_aggr(struct ath_softc *sc, struct ath_txq *txq,
> ath_reset(sc, false);
> }
>
> +static bool ath_lookup_lecacy(struct ath_buf *bf)
> +{
> + struct sk_buff *skb;
> + struct ieee80211_tx_info *tx_info;
> + struct ieee80211_tx_rate *rates;
> +
> + skb = bf->bf_mpdu;
> + tx_info = IEEE80211_SKB_CB(skb);
> + rates = tx_info->control.rates;
> +
> + /*
> + * Checking the last MRR's flag is sufficient to
> + * determine legacy or not
> + */
No it isn't. Maybe with ath9k_rate_control, but things may change with
other rate control modules.
- Felix
prev parent reply other threads:[~2011-08-22 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 12:37 [PATCH] ath9k: Send legacy rated frames as unaggregated Rajkumar Manoharan
2011-08-22 15:02 ` Felix Fietkau [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=4E526F78.1030302@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qca.qualcomm.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.