From: Ben Greear <greearb@candelatech.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
lrodriguez@atheros.com
Subject: Re: [PATCH 1/2] ath9k: try more than one tid when scheduling a new aggregate
Date: Tue, 18 Jan 2011 16:26:45 -0800 [thread overview]
Message-ID: <4D362FC5.3090003@candelatech.com> (raw)
In-Reply-To: <1295098215-98910-1-git-send-email-nbd@openwrt.org>
On 01/15/2011 05:30 AM, Felix Fietkau wrote:
> Sometimes the first TID in the first AC's list is not available for forming
> a new aggregate (the BAW might not allow it), however other TIDs may have
> data available for sending.
> Prevent a slowdown of other TIDs by going through multiple entries until
> we've either hit the last one or enough AMPDUs are pending in the hardware
> queue.
I had attempted a similar patch, but I was thinking we should iterate
through all of the txq->axq_acq entries, not just use the first one?
If you agree, I can merge my patch with your patch below
and re-post.
Thanks,
Ben
>
> Signed-off-by: Felix Fietkau<nbd@openwrt.org>
> ---
> drivers/net/wireless/ath/ath9k/xmit.c | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c
> index ab4f7b4..fffd13d 100644
> --- a/drivers/net/wireless/ath/ath9k/xmit.c
> +++ b/drivers/net/wireless/ath/ath9k/xmit.c
> @@ -1224,12 +1224,14 @@ void ath_tx_cleanupq(struct ath_softc *sc, struct ath_txq *txq)
> void ath_txq_schedule(struct ath_softc *sc, struct ath_txq *txq)
> {
> struct ath_atx_ac *ac;
> - struct ath_atx_tid *tid;
> + struct ath_atx_tid *tid, *last;
>
> - if (list_empty(&txq->axq_acq))
> + if (list_empty(&txq->axq_acq) ||
> + txq->axq_ampdu_depth>= ATH_AGGR_MIN_QDEPTH)
> return;
>
> ac = list_first_entry(&txq->axq_acq, struct ath_atx_ac, list);
> + last = list_entry(ac->tid_q.prev, struct ath_atx_tid, list);
> list_del(&ac->list);
> ac->sched = false;
>
> @@ -1253,7 +1255,8 @@ void ath_txq_schedule(struct ath_softc *sc, struct ath_txq *txq)
> if (!list_empty(&tid->buf_q))
> ath_tx_queue_tid(txq, tid);
>
> - break;
> + if (tid == last || txq->axq_ampdu_depth>= ATH_AGGR_MIN_QDEPTH)
> + break;
> } while (!list_empty(&ac->tid_q));
>
> if (!list_empty(&ac->tid_q)) {
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-01-19 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 13:30 [PATCH 1/2] ath9k: try more than one tid when scheduling a new aggregate Felix Fietkau
2011-01-15 13:30 ` [PATCH 2/2] ath9k: fix excessive BAR sending when a frame exceeds its retry limit Felix Fietkau
2011-01-19 0:26 ` Ben Greear [this message]
2011-01-19 0:33 ` [PATCH 1/2] ath9k: try more than one tid when scheduling a new aggregate Felix Fietkau
2011-01-19 0:43 ` Ben Greear
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=4D362FC5.3090003@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=nbd@openwrt.org \
/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).