From: Ryan Hsu <ryanhsu@qti.qualcomm.com>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Ryan Hsu <ryanhsu@qti.qualcomm.com>,
Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Networking <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: WARN_ON_ONCE(work > weight) in napi_poll()
Date: Tue, 18 Jul 2017 06:47:09 +0000 [thread overview]
Message-ID: <daa2fbf9-ac75-a7eb-f2b7-054dfae6fc56@qca.qualcomm.com> (raw)
In-Reply-To: <3ce246b3-b110-dd50-bf29-45ee78985872@quantenna.com>
On 07/11/2017 06:19 PM, Igor Mitsyanko wrote:
> On 07/11/2017 10:28 AM, Andrey Ryabinin wrote:
>>
>> It gave me this:
>>
>> [118648.825347] #1 quota too big 72 64 16
>> [118648.825351] #2 quota too big 72 64 16
>> [118648.825471] ------------[ cut here ]------------
>> [118648.825484] WARNING: CPU: 0 PID: 0 at ../net/core/dev.c:5274 net_rx_=
action+0x258/0x360
>>
>> So this means that we didn't met the condition bellow, i.e. skb_queue_em=
pty() returned true.
>>
>> ath10k_htt_txrx_compl_task():
>>
>> if ((quota > ATH10K_NAPI_QUOTA_LIMIT) &&
>> !skb_queue_empty(&htt->rx_in_ord_compl_q)) {
>> resched_napi =3D true;
>> goto exit;
>> }
>>
>>> Also WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware is a bit old, could you als=
o update firmware to give it a try?
>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>
>>
>> Will try.
>>
>
> Maybe ath10k_htt_rx_in_ord_ind() has to accept "budget_left" parameter an=
d use it to limit number of processed MSDUs in queued AMSDU and saving rest=
for later (NAPI has to be rescheduled in this case).
> It seems natural that this problem happens with current logic, in case AM=
SDU in Rx queue has more elements then left in budget.
Thanks, likely in current logic, it does have chance to exceed the budget w=
hile dequeuing from the last list.
Can you give it a try this one? for QCA6174 reorder is offload, so this sho=
uld be good enough for your case to test, will have to check non-offload re=
order case... but let me know if you're seeing something different....
--
diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireles=
s/ath/ath10k/htt_rx.c
index 398dda9..e8697a1 100644
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -1735,7 +1735,8 @@ static void ath10k_htt_rx_delba(struct ath10k *ar, st=
ruct htt_resp *resp)
}
=20
static int ath10k_htt_rx_extract_amsdu(struct sk_buff_head *list,
- struct sk_buff_head *amsdu)
+ struct sk_buff_head *amsdu,
+ int budget_left)
{
struct sk_buff *msdu;
struct htt_rx_desc *rxd;
@@ -1746,8 +1747,9 @@ static int ath10k_htt_rx_extract_amsdu(struct sk_buff=
_head *list,
if (WARN_ON(!skb_queue_empty(amsdu)))
return -EINVAL;
=20
- while ((msdu =3D __skb_dequeue(list))) {
+ while ((msdu =3D __skb_dequeue(list)) && budget_left) {
__skb_queue_tail(amsdu, msdu);
+ budget_left--;
=20
rxd =3D (void *)msdu->data - sizeof(*rxd);
if (rxd->msdu_end.common.info0 &
@@ -1838,7 +1840,8 @@ static int ath10k_htt_rx_h_rx_offload(struct ath10k *=
ar,
return num_msdu;
}
=20
-static int ath10k_htt_rx_in_ord_ind(struct ath10k *ar, struct sk_buff *skb=
)
+static int ath10k_htt_rx_in_ord_ind(struct ath10k *ar, struct sk_buff *skb=
,
+ int budget_left)
{
struct ath10k_htt *htt =3D &ar->htt;
struct htt_resp *resp =3D (void *)skb->data;
@@ -1895,9 +1898,9 @@ static int ath10k_htt_rx_in_ord_ind(struct ath10k *ar=
, struct sk_buff *skb)
if (offload)
num_msdus =3D ath10k_htt_rx_h_rx_offload(ar, &list);
=20
- while (!skb_queue_empty(&list)) {
+ while (!skb_queue_empty(&list) && budget_left) {
__skb_queue_head_init(&amsdu);
- ret =3D ath10k_htt_rx_extract_amsdu(&list, &amsdu);
+ ret =3D ath10k_htt_rx_extract_amsdu(&list, &amsdu, budget_left);
switch (ret) {
case 0:
/* Note: The in-order indication may report interleaved
@@ -1907,6 +1910,7 @@ static int ath10k_htt_rx_in_ord_ind(struct ath10k *ar=
, struct sk_buff *skb)
* should still give an idea about rx rate to the user.
*/
num_msdus +=3D skb_queue_len(&amsdu);
+ budget_left -=3D skb_queue_len(&amsdu);
ath10k_htt_rx_h_ppdu(ar, &amsdu, status, vdev_id);
ath10k_htt_rx_h_filter(ar, &amsdu, status);
ath10k_htt_rx_h_mpdu(ar, &amsdu, status);
@@ -2549,7 +2553,8 @@ int ath10k_htt_txrx_compl_task(struct ath10k *ar, int=
budget)
}
=20
spin_lock_bh(&htt->rx_ring.lock);
- num_rx_msdus =3D ath10k_htt_rx_in_ord_ind(ar, skb);
+ num_rx_msdus =3D ath10k_htt_rx_in_ord_ind(ar, skb,
+ (budget - quota));
spin_unlock_bh(&htt->rx_ring.lock);
if (num_rx_msdus < 0) {
resched_napi =3D true;
--
--=20
Ryan Hsu
next prev parent reply other threads:[~2017-07-18 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 16:34 WARN_ON_ONCE(work > weight) in napi_poll() Andrey Ryabinin
2017-07-04 13:49 ` Kalle Valo
2017-07-04 15:59 ` Andrey Ryabinin
2017-07-10 21:24 ` Ryan Hsu
2017-07-11 17:28 ` Andrey Ryabinin
2017-07-12 1:19 ` Igor Mitsyanko
2017-07-18 6:47 ` Ryan Hsu [this message]
2017-07-24 9:30 ` Andrey Ryabinin
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=daa2fbf9-ac75-a7eb-f2b7-054dfae6fc56@qca.qualcomm.com \
--to=ryanhsu@qti.qualcomm.com \
--cc=aryabinin@virtuozzo.com \
--cc=ath10k@lists.infradead.org \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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).