Hi Gao,
Thanks for the review. I have addressed the comments and
did further cleanup in v3 at
https://lore.kernel.org/linux-erofs/20250422234546.2932092-1-dhav...@google.com/
Thanks,
Sandeep.
Hi,
On 2025/4/3 04:27, 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 devi
On Mon, Apr 7, 2025 at 8:07 PM Gao Xiang wrote:
>
> Hi Sandeep,
>
Hi Gao,
> On 2025/4/8 10:53, Sandeep Dhavale wrote:
> > Hi,
> > Gentle ping for review in case this slipped through the list.
>
> I'm working on internal stuffs (unrelated to erofs,
> currently I have to handle erofs stuffs totally
Hi Sandeep,
On 2025/4/8 10:53, Sandeep Dhavale wrote:
Hi,
Gentle ping for review in case this slipped through the list.
I'm working on internal stuffs (unrelated to erofs,
currently I have to handle erofs stuffs totally in my
spare time), also does it really need to be resolved now?
It's not
Hi,
Gentle ping for review in case this slipped through the list.
Thanks,
Sandeep.
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 cha
