(Change announced on 2013-07-15)
(Change Proposal ready for 2013-07-24 FESCo meeting (#1145))
|Line 79:||Line 79:|
Revision as of 12:25, 23 July 2013
Using recent kernel (3.9 and later) features for (fast) SSD caching of (slow) ordinary hard disks.
- Name: Rolf Fokkens
- Email: firstname.lastname@example.org
- Release notes owner:
- Targeted release: Fedora 20
- Last updated: 2013-07-08
- Tracker bug: <will be assigned by the Wrangler>
Recent Linux kernels support the use of Solid State Drives as caches for rotational hard disks. Because the high cost per GB for SSD devices this feature may bring the best of both: fast end big yet affordable storage capacity. Linux kernel 3.9 introduced dm-cache, kernel 3.10 introduces bcache.
Benefit to Fedora
Fedora will support SSD's in a way that brings the speed of SSD's to the user, while also bringing the capacity of HDD's. The user however does not need to plan what data to put where (SSD or HDD): the Linux kernel will take care of that based on the usage patern.
- Proposal owners: Enable caching features in new kernels
- Other developers: Support the caching features in their respective packages. Special focus should be on making the system boot from a cached root FS.
- Release engineering: All packages should operate in close harmony te make this work. Only a rebuild of the relevant packages is required.
- Policies and guidelines: No changes I think.
Implementing a caching root FS requires a reinstall for sure, because caching requires its own superblock on disks/volumes!
All existing Fedora functionality remains as is.
How To Test
Testing involves doing a clean install of Fedora, while configuring in anaconda a cached root FS. After the installation the cache state should be checked (if it is operational or not.
- run benchmarks (see performance improvement over non cached storage)
- update the kernel (see if dracut builds a functional initramfs including caching
Users should experience improved storage performance.
Although the kernel supports SSD caching, the other mentioned packages should be changed to support this and make it really work.
- Contingency mechanism: Revert the shipped configuration of the relevant packages.
- Contingency deadline: beta freeze
- Blocks release? No