From: Dmitry Osipenko <digetx@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
linux-wireless@vger.kernel.org, brcm80211-dev-list@broadcom.com,
brcm80211-dev-list@cypress.com,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Wright Feng <wright.feng@cypress.com>,
Amar Shankar <amsr@cypress.com>,
Jia-Shyr Chuang <joseph.chuang@cypress.com>
Subject: Re: [PATCH V2 3/6] brcmfmac: reserve 2 credits for host tx control path
Date: Tue, 4 Aug 2020 18:53:20 +0300 [thread overview]
Message-ID: <ffcf55cc-b27d-78ec-ff4f-e7efa3087712@gmail.com> (raw)
In-Reply-To: <875z9yr7lg.fsf@codeaurora.org>
04.08.2020 14:08, Kalle Valo пишет:
> Dmitry Osipenko <digetx@gmail.com> writes:
>
>> 10.06.2020 18:21, Chi-Hsien Lin пишет:
>>> From: Amar Shankar <amsr@cypress.com>
>>>
>>> It is observed that sometimes when sdiod is low in tx credits in low
>>> rssi scenarios, the data path consumes all sdiod rx all credits and
>>> there is no sdiod rx credit available for control path causing host
>>> and card to go out of sync resulting in link loss between host and
>>> card. So in order to prevent it some credits are reserved for control
>>> path.
>>>
>>> Note that TXCTL_CREDITS can't be larger than the firmware default
>>> credit update threshold 2; otherwise there will be a deadlock for both
>>> side waiting for each other.
>>>
>>> Signed-off-by: Amar Shankar <amsr@cypress.com>
>>> Signed-off-by: Jia-Shyr Chuang <joseph.chuang@cypress.com>
>>> Signed-off-by: Chi-Hsien Lin <chi-hsien.lin@cypress.com>
>
> [...]
>
>> This patch causes a severe WiFi performance regression on BCM4329.
>> Please fix or revert this patch, thanks in advance.
>>
>> Before this patch:
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID] Interval Transfer Bitrate Retr
>> [ 5] 0.00-10.00 sec 17.2 MBytes 14.4 Mbits/sec 0 sender
>> [ 5] 0.00-10.04 sec 16.9 MBytes 14.1 Mbits/sec
>> receiver
>>
>>
>> After this patch:
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID] Interval Transfer Bitrate Retr
>> [ 5] 0.00-10.00 sec 1.05 MBytes 881 Kbits/sec 3 sender
>> [ 5] 0.00-14.01 sec 959 KBytes 561 Kbits/sec
>> receiver
>
> Can someone please send a revert patch (with the explanation above) if a
> fix is not quickly found? The commit id is:
>
> commit b41c232d33666191a1db11befc0f040fcbe664e9
> Author: Amar Shankar <amsr@cypress.com>
> AuthorDate: Wed Jun 10 10:21:03 2020 -0500
> Commit: Kalle Valo <kvalo@codeaurora.org>
> CommitDate: Tue Jul 14 12:46:43 2020 +0300
>
> brcmfmac: reserve 2 credits for host tx control path
>
Hello Kalle,
I'll send the revert if nobody will stand up to address the problem in a
two weeks, thanks.
next prev parent reply other threads:[~2020-08-04 15:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:21 [PATCH V2 0/6] brcmfmac: flow control and p2p fix series Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 1/6] brcmfmac: allow credit borrowing for all access categories Chi-Hsien Lin
2020-07-14 9:47 ` Kalle Valo
2020-06-10 15:21 ` [PATCH V2 2/6] brcmfmac: increase message buffer size for control packets Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 3/6] brcmfmac: reserve 2 credits for host tx control path Chi-Hsien Lin
2020-08-03 16:27 ` Dmitry Osipenko
2020-08-04 11:08 ` Kalle Valo
2020-08-04 15:53 ` Dmitry Osipenko [this message]
2020-08-04 17:22 ` Kalle Valo
2020-08-05 8:24 ` Chi-Hsien Lin
2020-08-05 14:01 ` Dmitry Osipenko
2020-08-11 8:35 ` Wright Feng
2020-08-11 14:54 ` Dmitry Osipenko
2020-08-12 4:03 ` Wright Feng
2020-08-12 14:22 ` Dmitry Osipenko
2020-08-13 3:03 ` Wright Feng
2020-08-13 21:30 ` Dmitry Osipenko
2020-06-10 15:21 ` [PATCH V2 4/6] brcmfmac: update tx status flags to sync with firmware Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 5/6] brcmfmac: fix throughput zero stalls on PM 1 mode due to credit map Chi-Hsien Lin
2020-06-10 15:21 ` [PATCH V2 6/6] brcmfmac: initialize the requested dwell time Chi-Hsien Lin
2020-06-22 15:04 ` Chi-Hsien Lin
2020-07-14 9:30 ` Kalle Valo
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=ffcf55cc-b27d-78ec-ff4f-e7efa3087712@gmail.com \
--to=digetx@gmail.com \
--cc=amsr@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=joseph.chuang@cypress.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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 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).