[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#618029: Uses gzip compression for the uInitrd which is already zipped

severity 618029 wishlist


 Thibaut Girka helpfully pointed out that "-C gzip" is just a data flag
 to mkimage that wont do any compression itself.  However, U-Boot does
 seem to be doing decompression of "multi" images (at load time) and of
 the initrd (at bootm time).  It seems that both options are open for
 the initrd, and some might be faster than others (for instance U-Boot
 recently gained support for L2 cache on some CPU so that decompression
 is much faster as the code and data stays in the caches), but there is
 no case of double-gzip or double-gunzip as I initially feared, hence
 lowering severity.

 We could look at boot speed and various compression options to make the
 best compromise of size of the U-Boot images and boot time.


On Sun, Mar 13, 2011, Loïc Minier wrote:
>  flash-kernel currently calls mkimage -C gzip when creating uInitrds for
>  various platforms, but Debian initrds are already gzipped by
>  initramfs-tools, so it seems like a waste of CPU cycles at flash-kernel
>  and boot time.
>    Cheers,
> -- 
> Loïc Minier

Loïc Minier

Reply to: