From: Chao Yu <chao@kernel.org>
To: Sandeep Dhavale <dhavale@google.com>,
linux-erofs@lists.ozlabs.org, Gao Xiang <xiang@kernel.org>,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>
Cc: chao@kernel.org, hsiangkao@linux.alibaba.com,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] erofs: lazily initialize per-CPU workers and CPU hotplug hooks
Date: Tue, 6 May 2025 10:53:37 +0800 [thread overview]
Message-ID: <96b206b2-4808-4cbb-960c-016b07dec3bf@kernel.org> (raw)
In-Reply-To: <20250501183003.1125531-1-dhavale@google.com>
On 2025/5/2 2:30, Sandeep Dhavale wrote:
> Currently, when EROFS is built with per-CPU workers, the workers are
> started and CPU hotplug hooks are registered during module initialization.
> This leads to unnecessary worker start/stop cycles during CPU hotplug
> events, particularly on Android devices that frequently suspend and resume.
>
> This change defers the initialization of per-CPU workers and the
> registration of CPU hotplug hooks until the first EROFS mount. This
> ensures that these resources are only allocated and managed when EROFS is
> actually in use.
>
> The tear down of per-CPU workers and unregistration of CPU hotplug hooks
> still occurs during z_erofs_exit_subsystem(), but only if they were
> initialized.
>
> Signed-off-by: Sandeep Dhavale <dhavale@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-05-06 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 18:30 [PATCH v5] erofs: lazily initialize per-CPU workers and CPU hotplug hooks Sandeep Dhavale
2025-05-06 2:53 ` Chao Yu [this message]
2025-05-06 3:30 ` Gao Xiang
2025-05-06 23:02 ` Sandeep Dhavale
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=96b206b2-4808-4cbb-960c-016b07dec3bf@kernel.org \
--to=chao@kernel.org \
--cc=dhavale@google.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=kernel-team@android.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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