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...
-- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
