On Fri, Dec 30, 2011 at 1:37 PM, Dave Jones <davej@xxxxxxxxxx> wrote: > On Fri, Dec 30, 2011 at 11:23:58AM +0100, Michal Marek wrote: > > On 29.12.2011 18:21, Dave Jones wrote: > > > On Thu, Dec 29, 2011 at 01:50:18PM -0200, Lucas De Marchi wrote: > > > > Add target in Makefile to compress the module after it's installed. > > > > Module-init-tools and libkmod can handle gzipped modules. > > > > > > > > This is not much useful for distributions because the package will gzip > > > > the modules and call depmod in a install rule. > > > > > > It might actually be a worthwhile thing for distributions. > > > > > > For a Fedora kernel, gzipping modules saves around 80MB of diskspace per > > > installed kernel. That the RPM is compressed is irrelevant, the on-disk > > > footprint is more interesting, given that the bulk of the modules installed > > > will never even be loaded. > > > > But it kills performance of the tools. > > How often do you run depmod ? > > If modprobe is a bottleneck, you have other problems. modprobe is not a problem because it needs to read the entire blob to insert regardless. The only affected tools would be depmod and modinfo, but if this is really a problem, we could change the loader of gz and xz files to stop when the ".modinfo" section was read for the modinfo command. As I said, I don't want to debate here whether it's good or not to have compressed modules. It would be nice though to cook up some numbers on different setups with the different compression methods (none, gz, xz). Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
