From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
Sriram R <srirrama@codeaurora.org>
Subject: Re: [PATCH] ath11k: Add dynamic tcl ring selection logic with retry mechanism
Date: Wed, 15 Apr 2020 08:07:52 +0000 (UTC) [thread overview]
Message-ID: <20200415080753.02F66C43636@smtp.codeaurora.org> (raw)
In-Reply-To: <1586782622-22570-1-git-send-email-srirrama@codeaurora.org>
Sriram R <srirrama@codeaurora.org> wrote:
> IPQ8074 HW supports three TCL rings for tx. Currently these rings
> are mapped based on the Access categories, viz. VO, VI, BE, BK.
> In case, one of the traffic type dominates, then it could stress
> the same tcl rings. Rather, it would be optimal to make use of all
> the rings in a round robin fashion irrespective of the traffic type
> so that the load could be evenly distributed among all the rings.
> Also, in case the selected ring is busy or full, a retry mechanism
> is used to ensure other available ring is selected without dropping
> the packet.
>
> In SMP systems, this change avoids a single CPU from getting hogged
> when heavy traffic of same category is transmitted.
> The tx completion interrupts corresponding to the used tcl ring
> would be more which causes the assigned CPU to get hogged.
> Distribution of tx packets to different tcl rings helps balance
> this load.
>
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
d687275b268b ath11k: Add dynamic tcl ring selection logic with retry mechanism
--
https://patchwork.kernel.org/patch/11485549/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-04-15 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 12:57 [PATCH] ath11k: Add dynamic tcl ring selection logic with retry mechanism Sriram R
2020-04-13 12:57 ` Sriram R
2020-04-15 8:07 ` Kalle Valo
2020-04-15 8:07 ` Kalle Valo [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=20200415080753.02F66C43636@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=srirrama@codeaurora.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 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.