diff options
| author | John Crispin <blogic@openwrt.org> | 2014-06-02 12:43:46 +0000 |
|---|---|---|
| committer | John Crispin <blogic@openwrt.org> | 2014-06-02 12:43:46 +0000 |
| commit | d4d63a3d241b453a044ce72a5bb7ea68e94f7b2c (patch) | |
| tree | 5e8127f47766a36ca113143151c372a5abce66a4 /tools/m4 | |
| parent | 4c58e12447b930bbaa8747a03a41707177e3bc00 (diff) | |
| download | master-187ad058-d4d63a3d241b453a044ce72a5bb7ea68e94f7b2c.tar.gz master-187ad058-d4d63a3d241b453a044ce72a5bb7ea68e94f7b2c.tar.bz2 master-187ad058-d4d63a3d241b453a044ce72a5bb7ea68e94f7b2c.zip | |
tools: genext2fs: add support for blocksize != 1024
This patch series is extracted from
http://ftp.de.debian.org/debian/pool/main/g/genext2fs/genext2fs_1.4.1-4.debian.tar.gz
The patches are used in Debian for quite a long time, so I assume that
this is solid material. At least, my Ubuntu host fsck.ext4 does not bark :-)
The goal is to allow building filesystems with larger blocksizes instead of the
current default of 1k. This should improve performance and lifetime when the
filesystem is stored e.g. on a SD card (on Raspberry Pi/I2SE Duckbill for example)
which uses internal flash memory. Writing to flash memory is slow because writing
the data of one block results in erasing a whole erase block of the flash memory.
Thus it is preferable to align the filesystem block size on a flash device with
the erase blocksize, or at least bring it closer to the later one, to avoid
unnecessary write amplification.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@40921 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'tools/m4')
0 files changed, 0 insertions, 0 deletions