On Monday 16 Nov 2015 12:38:27 Chandan Rajendra wrote: > Btrfs assumes block size to be the same as the machine's page > size. This would mean that a Btrfs instance created on a 4k page size > machine (e.g. x86) will not be mountable on machines with larger page > sizes (e.g. PPC64/AARCH64). This patchset aims to resolve this > incompatibility. > > This patchset continues with the work posted previously at > https://lwn.net/Articles/646937/. > > I have reverted the upstream commit "btrfs: fix lockups from > btrfs_clear_path_blocking" (f82c458a2c3ffb94b431fc6ad791a79df1b3713e) > since this led to soft-lockups when the patch "Btrfs: > subpagesize-blocksize: Prevent writes to an extent buffer when > PG_writeback flag is set" is applied. > > The commits for the Btrfs kernel module can be found at > https://github.com/chandanr/linux/tree/btrfs/subpagesize-blocksize. > > The commits for Btrfs-progs can be found at > https://github.com/chandanr/btrfs-progs/tree/btrfs/subpagesize-blocksize. > > Changes from V11: > 1. Addressed the review comments provided by Liu Bo for version V11. > 2. Fixed file defragmentation code to work in subpagesize-blocksize > scenario. > 3. Many "hard to reproduce" bugs were fixed. > > fstests run status: > 1. On x86_64, all the tests (i.e. both generic and btrfs specific > tests) pass > - With 2k and 4k data blocksize combinations. > - With and without nodatacow option. > 2. On ppc64, generic tests were run with 4k data block size and 16k > metadata block size. generic/300 fails because of an issue with the > fio tool. The failure is seen even when running the test for other > filesystems (i.e. ext4 and xfs). One more mistake from my side. On x86_64, For 2k block size, only generic tests were run (since the goal was to get regular I/O upstreamed first and then get the features upstreamed in subsequent releases). However, On x86_64, with 4k block size, all the tests (i.e. generic and btrfs specific) pass indicating that the changes do not cause any regression in other Btrfs features. -- chandan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
