[LSF/MM TOPIC]: Btrfs: Decoupling block-size and page-size in BTRFS.

* [LSF/MM TOPIC]: Btrfs: Decoupling block-size and page-size in BTRFS.
@ 2014-11-27  7:13 Chandan Rajendra
  2014-12-01 10:13 ` [Lsf-pc] " Christoph Hellwig
  0 siblings, 1 reply; 3+ messages in thread
From: Chandan Rajendra @ 2014-11-27  7:13 UTC (permalink / raw)
  To: lsf-pc; +Cc: linux-fsdevel, linux-btrfs

In BTRFS, BLOCK_SIZE, the basic IO size of the filesystem, is equal to the
PAGE_SIZE of the architecture. Some 64-bit architectures, like PPC64 and
ARM64, can/do have a default PAGE_SIZE of 64K, which means the filesystems
handled in these architectures have a BLOCK_SIZE of 64K.

This works fine as long as you create and use the filesystems within
these systems. But users cannot create a filesystem in an architecture
of a specific BLOCK_SIZE and then use that filesystem in another. So a
filesystem created on x86 cannot be used (mounted, read, ...) on a
PPC64 or ARM64 system.

9 versions of the subpagesize-blocksize patchset have been posted until today
(see
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg38862.html). These
patches address only the issues in regular I/O code path of Btrfs and still
needs more work to get it working correctly. Other Btrfs features
(e.g. compression, scrub, etc) also need some work to get them working in
subpagesize-blocksize scenario.

I believe that a face-to-face discussion involving Btrfs
maintainers/developers to address some of the design issues would enable us to
fast track the inclusion of this feature into the mainline kernel tree.

-- 
chandan

^ permalink raw reply	[flat|nested] 3+ messages in thread