From Fedora Project Wiki
(Sources to indicate that 2.6.34 does not have support for lzma squashfs despite what kernelnewbies says)
No edit summary
Line 11: Line 11:
== Current status ==
== Current status ==
* Targeted release: [[Releases/14 | Fedora 14 ]]
* Targeted release: [[Releases/14 | Fedora 14 ]]
* Last updated: 2010-02-14
* Last updated: 2010-06-04
* Percentage of completion: 40%
* Percentage of completion: 40%



Revision as of 17:38, 7 June 2010

LZMA for Live Images

Summary

Better compression technology (LZMA) allows us to ship more software on our live images.

Owner

  • Email: <bruno@wolff.to>

Current status

  • Targeted release: Fedora 14
  • Last updated: 2010-06-04
  • Percentage of completion: 40%

Detailed Description

LZMA compression typically provides better compression than zlib while still providing relatively fast uncompression. Once squashfs file systems are supported by the kernel we can use them for building live images. A test with the games spin resulted in a 10% reduction in size of the resulting live image.

Benefit to Fedora

By allowing more packages to be put on a Live Image, we can make a few of our space constrained images better. For other images, having them be smaller will make them faster to download.

Scope

  • Lougher needs to do a new set of patches since the ones for 2.6.34 were only partially accepted.
    • Patches for 2.6.35 were not supplied during the merge window. This makes it unlikely that they will be accepted for 2.6.35 and that 2.6.36 will be the next chance. If the patches do get accepted for 2.6.36, we can probably have the squashfs support in place for the release (maybe backporting patches, since F14 will probably release with 2.6.35). I'll need to have squashfs and livecd-creator updates ready to go if I need to wait until the 2.6.36 merge window to know if the feature will be doable or not as there will be little time after that to get it working.
    • Statements from Lougher:
  • Lougher's 4.1 (currently prerelease) version of squashfs-tools needs to be in the release.
    • Bug 504425 documents the current status of that effort.
      • It currently builds.
      • It uses multiple processors for both zlib and lzma compression.
      • A test games spin had a 10% reduction (from almost 4.4 GB to just under 4 GB) in size using lzma compression, saving about 400 MB. (This was a nonfunctional image because of lack of kernel support for lzma squashfs.)
      • A live image was built using this version of squashfs (using the default zlib compression) which functioned properly. No changes were made to livecd-creator to make the image.
      • Currently there is just a scratch build of the dev squashfs-tools.
  • livecd-creator needs to be modified to have mksquashfs use lzma compression. (Probably as the default, with other compression methods specifiable as command line options.)
  • If possible this should be usable significantly ahead of feature freeze so that spin owners can be pretty safe relying on it for their spins.

How To Test

  • We need to make sure live images work.
  • We need to make sure live images are smaller using LZMA compression.
  • We need to make sure performance is acceptable. (I.e. that LZMA doesn't slow things down significantly on typical systems.)

User Experience

Live images will be smaller or have more included packages.

Dependencies

  • squashfs-tools
  • kernel (may need to ask for backport)
  • livecd-tools

Contingency Plan

  • Since the default in the new squashfs is to use zlib compression, we shouldn't have to revert squashfs-tools.
  • livecd-creator would need to have at least some of the changes reverted.

Documentation

  • Most likely livecd-creator would be getting a new option and would need its help updated along with the code changes.

Release Notes

  • Mention the squashfs version change, that it supports LZMA compression, point to its documentation and note that it is supported in the kernel as well.
  • Mention that livecd-creator uses LZMA by default, how to get zlib compression if desired for use with older kernels or other reasons.

Comments and Discussion