[Bug 433015] New: mkinitrd performance / module list changes
https://bugzilla.novell.com/show_bug.cgi?id=433015 Summary: mkinitrd performance / module list changes Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: hare@novell.com ReportedBy: agruen@novell.com QAContact: qa@suse.de CC: jsrain@novell.com, mmarek@novell.com, jreidinger@novell.com Found By: --- An initrd contains a list of modules for the boot kernel. There are a number of situations in which that list changes, and the initrd needs to be updated: * Kernel packages get installed (so the initrd can be created), or updated (modules may get replaced. * The modprobe.conf configuration changes (for blocking particular modules or changing the priorities among several compatible modules). * Kernel module packages (kmps) get installed, replacing existing modules or making required modules available. Previously, KMPs were the major triggers for recreating initrds, but with the recent kernel package split, the number of cases in which we may need to recreate the initrd has increased. The heuristics for figuring out when recreating the initrd is necessary are all more or less broken, and so we will en dup running mkinitrd repeatedly during a normal system install, during kernel package updated, and during KMP installs, even if the initrd isn't actually affected. With the current mkinitrd, this will be slow. I propose to change mkinitrd as follows to speed things up: * When creating an initrd, in addition to what mkinitrd does now, it saves the list of kernel modules used into a separate file, including the file size and time of last modification (stat --format='%Y %s %n' or similar). * When asked to create the same initrd again, it computes the same list, and before actually recreating the initrd, it checks if the old and new lists are the same. If the lists are the same (and none of the mkinitrd scriptlets have changed, the initrd file still exists and hasn't changed itself, etc.), mkinitrd simply does nothing. This would allow us to get rid of the weak heuristics currently used. Does this sound acceptable? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c1 --- Comment #1 from Andreas Gruenbacher <agruen@novell.com> 2008-10-07 06:28:04 MDT --- We would preferably need this in Beta3, but if it can't be implemented by then, some of the package installs will simply become slower. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c2 --- Comment #2 from Michal Marek <mmarek@novell.com> 2008-10-08 01:05:03 MDT --- For now, the new weak-modules script in m-i-t will check which modules are in the initrd and run mkinitrd only if a kmp changed one of these modules. This should do the right thing for KMPs, but not for kernel (sub)packages (kernel-$flavor-base creates a minimal inintrd, applying the above logic would keep that initrd unchanged even after installing kernel-$flavor. Some smartness in mkinitrd would therefore help a lot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c3 --- Comment #3 from Andreas Gruenbacher <agruen@novell.com> 2008-10-08 01:24:51 MDT --- Okay, thanks. I nevertheless think that implementing the up-to-date check in mkinitrd would be much better, and would replace the heuristics with the "real thing". It doesn't seem hard to implement or test, either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com AssignedTo|hare@novell.com |agraf@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 Alexander Graf <agraf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|agraf@novell.com |bwalle@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 Bernhard Walle <bwalle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Component|Basesystem |Basesystem Priority|P5 - None |P3 - Medium Product|openSUSE 11.1 |openSUSE 11.2 Version|Factory |unspecified -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 Bernhard Walle <bwalle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User bwalle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c4 Bernhard Walle <bwalle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aosthof@novell.com Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #4 from Bernhard Walle <bwalle@novell.com> 2008-12-12 07:53:33 MST --- Please open a FATE for that. That's not to be done in 10 minutes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c5 Andreas Gruenbacher <agruen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #5 from Andreas Gruenbacher <agruen@novell.com> 2008-12-12 08:38:57 MST --- Not very clever to resolve this as invalid when it needs further tracking ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 Andreas Gruenbacher <agruen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bwalle@novell.com |agruen@novell.com Status|REOPENED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=433015 User bwalle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=433015#c6 --- Comment #6 from Bernhard Walle <bwalle@novell.com> 2008-12-12 08:46:17 MST --- I just wanted that to go through the FATE process. Also, we need to decide if we put resources in the new mainline initrd or in our initrd. Both at the same time is impossible for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com