public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Arend van Spriel <arend.vanspriel@broadcom.com>,
	Franky Lin <franky.lin@broadcom.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>,
	Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
	Wright Feng <wright.feng@cypress.com>,
	brcm80211-dev-list@cypress.com,
	brcm80211-dev-list.pdl@broadcom.com,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Broadcom WiFi SDIO performance regression after commit "mmc: sdhci: Remove finish_tasklet"
Date: Thu, 27 Aug 2020 12:36:40 +0300	[thread overview]
Message-ID: <eec0c7d2-87f3-1213-dec1-bb34c5bde35a@gmail.com> (raw)
In-Reply-To: <9332715c-6ee5-fce3-8b93-305823d5a551@intel.com>

27.08.2020 09:45, Adrian Hunter пишет:
> On 27/08/20 9:07 am, Dmitry Osipenko wrote:
>> Hello!
>>
>> I was debugging WiFi performance problems on Acer A500 tablet device
>> that has BCM4329 WiFi chip which is connected to NVIDIA Terga20 SoC via
>> SDIO and found that the following commit causes a solid 5-10 Mbit/s of
>> WiFi throughput regression after 5.2 kernel:
> 
> What is that in percentage terms?

That is about 20%.

>> commit c07a48c2651965e84d35cf193dfc0e5f7892d612
>> Author: Adrian Hunter <adrian.hunter@intel.com>
>> Date:   Fri Apr 5 15:40:20 2019 +0300
>>
>>     mmc: sdhci: Remove finish_tasklet
>>
>>     Remove finish_tasklet. Requests that require DMA-unmapping or
>> sdhci_reset
>>     are completed either in the IRQ thread or a workqueue if the
>> completion is
>>     not initiated by the IRQ.
>>
>> Reverting the offending commit on top of recent linux-next resolves the
>> problem.
>>
>> Ulf / Adrian, do you have any ideas what could be done in regards to
>> restoring the SDIO performance? Should we just revert the offending commit?
>>
> 
> Unfortunately I think we are past the point of returning to the tasklet.
> 
> sdhci can complete requests in the irq handler but only if ->pre_req() and
> ->post_req() are used, which is not supported by SDIO at present.  pre_req
> and post_req were introduced to reduce latency for the block driver, so it
> seems reasonable perhaps to look at using them in SDIO as well.
> 

I'll try to take a look at pre/post_req(), but I'm not very familiar
with the MMC code, so it may take quite some time. Will be great if you
could help with making a patch that I could test!

  reply	other threads:[~2020-08-27  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27  6:07 Broadcom WiFi SDIO performance regression after commit "mmc: sdhci: Remove finish_tasklet" Dmitry Osipenko
2020-08-27  6:45 ` Adrian Hunter
2020-08-27  9:36   ` Dmitry Osipenko [this message]
2020-08-31 15:08     ` Adrian Hunter
2020-08-31 18:53       ` Dmitry Osipenko

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=eec0c7d2-87f3-1213-dec1-bb34c5bde35a@gmail.com \
    --to=digetx@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@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=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=ulf.hansson@linaro.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