Brian Behlendorf 21ade34764 Disable direct reclaim for z_wr_* threads ... The direct reclaim path in the z_wr_* threads must be disabled to ensure forward progress is always maintained for txg processing. This ensures that a txg will never get stuck waiting on itself because it entered the following memory reclaim callpath. ->prune_icache()->dispose_list()->zpl_clear_inode()->zfs_inactive() ->dmu_tx_assign()->dmu_tx_wait()->tgx_wait_open() It would be preferable to target this exact code path but the kernel offers no way to do this without custom patches. To avoid this we are forced to disable all reclaim for these threads. It should not be necessary to do this for other other z_* threads because they will not hold a txg open. Closes #232		2011-05-06 15:26:26 -07:00
..
avl	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
nvpair	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
unicode	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
zcommon	Add basic uio support	2011-02-10 09:21:43 -08:00
zfs	Disable direct reclaim for z_wr_* threads	2011-05-06 15:26:26 -07:00
zpios	Linux 2.6.36 compat, use fops->unlocked_ioctl()	2010-11-10 17:01:08 -08:00
.gitignore	Add .gitignore files to exclude build products	2010-01-08 11:35:17 -08:00
Makefile.in	Fix make distclean for `./configure --with-config=user	2011-04-05 13:33:28 -07:00