diff options
| author | John Crispin <john@openwrt.org> | 2014-06-02 12:43:46 +0000 |
|---|---|---|
| committer | John Crispin <john@openwrt.org> | 2014-06-02 12:43:46 +0000 |
| commit | b6fbe7bd5da6548323030ced25582d90c7a99cc7 (patch) | |
| tree | 3b6bfae0ed3612370256faadda43848af26c85c8 /target/linux/avr32 | |
| parent | 7ba5188fe94b667cc17aeb010626c5d245a92aca (diff) | |
| download | mtk-20170518-b6fbe7bd5da6548323030ced25582d90c7a99cc7.zip mtk-20170518-b6fbe7bd5da6548323030ced25582d90c7a99cc7.tar.gz mtk-20170518-b6fbe7bd5da6548323030ced25582d90c7a99cc7.tar.bz2 | |
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>
SVN-Revision: 40921
Diffstat (limited to 'target/linux/avr32')
0 files changed, 0 insertions, 0 deletions