From: patchwork-bot+linux-arm-msm@kernel.org
To: Yogesh Lal <ylal@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V2] driver core: Use unbound workqueue for deferred probes
Date: Wed, 26 May 2021 19:03:28 +0000 [thread overview]
Message-ID: <162205580852.26840.97701715194819727.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1616583698-6398-1-git-send-email-ylal@codeaurora.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Wed, 24 Mar 2021 16:31:38 +0530 you wrote:
> Deferred probe usually runs only on pinned kworkers, which might take
> longer time if a device contains multiple sub-devices. One such case
> is of sound card on mobile devices, where we have good number of
> mixers and controls per mixer.
>
> We observed boot up improvement - deferred probes take ~600ms when bound
> to little core kworker and ~200ms when deferred probe is queued on
> unbound wq. This is due to scheduler moving the worker running deferred
> probe work to big CPUs. Without this change, we see the worker is running
> on LITTLE CPU due to affinity.
>
> [...]
Here is the summary with links:
- [V2] driver core: Use unbound workqueue for deferred probes
https://git.kernel.org/qcom/c/e611f8cd8717
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-26 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 11:01 [PATCH V2] driver core: Use unbound workqueue for deferred probes Yogesh Lal
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm [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=162205580852.26840.97701715194819727.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ylal@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.