mirror_zfs/config/kernel-bdi.m4

dnl #
dnl # 2.6.32 API change
dnl # Private backing_device_info interfaces available
dnl #
AC_DEFUN([ZFS_AC_KERNEL_BDI], [
	AC_MSG_CHECKING([whether super_block has s_bdi])
	ZFS_LINUX_TRY_COMPILE([
		#include <linux/fs.h>
	],[
		struct super_block sb __attribute__ ((unused));
		sb.s_bdi = NULL;
	],[
		AC_MSG_RESULT(yes)
		AC_DEFINE(HAVE_BDI, 1, [struct super_block has s_bdi])
	],[
		AC_MSG_RESULT(no)
	])
])
Add backing_device_info per-filesystem For a long time now the kernel has been moving away from using the pdflush daemon to write 'old' dirty pages to disk. The primary reason for this is because the pdflush daemon is single threaded and can be a limiting factor for performance. Since pdflush sequentially walks the dirty inode list for each super block any delay in processing can slow down dirty page writeback for all filesystems. The replacement for pdflush is called bdi (backing device info). The bdi system involves creating a per-filesystem control structure each with its own private sets of queues to manage writeback. The advantage is greater parallelism which improves performance and prevents a single filesystem from slowing writeback to the others. For a long time both systems co-existed in the kernel so it wasn't strictly required to implement the bdi scheme. However, as of Linux 2.6.36 kernels the pdflush functionality has been retired. Since ZFS already bypasses the page cache for most I/O this is only an issue for mmap(2) writes which must go through the page cache. Even then adding this missing support for newer kernels was overlooked because there are other mechanisms which can trigger writeback. However, there is one critical case where not implementing the bdi functionality can cause problems. If an application handles a page fault it can enter the balance_dirty_pages() callpath. This will result in the application hanging until the number of dirty pages in the system drops below the dirty ratio. Without a registered backing_device_info for the filesystem the dirty pages will not get written out. Thus the application will hang. As mentioned above this was less of an issue with older kernels because pdflush would eventually write out the dirty pages. This change adds a backing_device_info structure to the zfs_sb_t which is already allocated per-super block. It is then registered when the filesystem mounted and unregistered on unmount. It will not be registered for mounted snapshots which are read-only. This change will result in flush-<pool> thread being dynamically created and destroyed per-mounted filesystem for writeback. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #174 2011-08-02 05:24:40 +04:00			`dnl #`
			`dnl # 2.6.32 API change`
			`dnl # Private backing_device_info interfaces available`
			`dnl #`
			`AC_DEFUN([ZFS_AC_KERNEL_BDI], [`
			`AC_MSG_CHECKING([whether super_block has s_bdi])`
			`ZFS_LINUX_TRY_COMPILE([`
			`#include <linux/fs.h>`
			`],[`
			`struct super_block sb __attribute__ ((unused));`
			`sb.s_bdi = NULL;`
			`],[`
			`AC_MSG_RESULT(yes)`
			`AC_DEFINE(HAVE_BDI, 1, [struct super_block has s_bdi])`
			`],[`
			`AC_MSG_RESULT(no)`
			`])`
			`])`