mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sandeep Dhavale <dhavale@google.com>
To: linux-erofs@lists.ozlabs.org, Gao Xiang <xiang@kernel.org>,
	 Chao Yu <chao@kernel.org>, Yue Hu <zbestahu@gmail.com>,
	 Jeffle Xu <jefflexu@linux.alibaba.com>,
	Sandeep Dhavale <dhavale@google.com>
Cc: hsiangkao@linux.alibaba.com, kernel-team@android.com,
	 linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/1] erofs: start per-CPU workers on demand
Date: Sun, 30 Mar 2025 19:20:07 -0700	[thread overview]
Message-ID: <20250331022011.645533-1-dhavale@google.com> (raw)

erofs currently starts per-CPU workers on module_init() which is not
necessary. This starting of resources on cpu hotplug and unplug
shows up in Android where the erofs in built-in and erofs is
not yet being used.

Following patch moves the creation of per-CPU workers on the first
mount and they are removed when on the last unmount.

I tested this with erofs-utils test as well as running reads on
erofs mountpoint while running aggressive cpu online/offline in a
loop, withoutn any issue.

Thanks,
Sandeep.

Sandeep Dhavale (1):
  erofs: lazily initialize per-CPU workers and CPU hotplug support

 fs/erofs/internal.h |  5 +++++
 fs/erofs/super.c    | 27 +++++++++++++++++++++++++++
 fs/erofs/zdata.c    | 35 +++++++++++++++++++++++------------
 3 files changed, 55 insertions(+), 12 deletions(-)

-- 
2.49.0.472.ge94155a9ec-goog


             reply	other threads:[~2025-03-31  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31  2:20 Sandeep Dhavale [this message]
2025-03-31  2:20 ` [PATCH v1 1/1] erofs: lazily initialize per-CPU workers and CPU hotplug hooks Sandeep Dhavale
2025-03-31  2:38   ` Gao Xiang
2025-03-31  3:14     ` Sandeep Dhavale
2025-03-31  3:28       ` Gao Xiang
2025-03-31  3:43         ` Sandeep Dhavale
2025-03-31  3:48         ` Gao Xiang

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=20250331022011.645533-1-dhavale@google.com \
    --to=dhavale@google.com \
    --cc=chao@kernel.org \
    --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

all inboxes | Powered by JetHome®