An optimisation could be simply to only send progress when it has changed:
In fsck_reader() (line 2701 of mountall.c) an old_progress variable could be set to the previous iteration's progress and plymouth_progress() only called when progress differed from old_progress...
An optimisation could be simply to only send progress when it has changed:
In fsck_reader() (line 2701 of mountall.c) an old_progress variable could be set to the previous iteration's progress and plymouth_progress() only called when progress differed from old_progress...