xfs: allow writeback from kswapd
We only need disable I/O from direct or memcg reclaim. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
This commit is contained in:
parent
651701d71d
commit
d4f7a5cbd5
|
@ -1049,16 +1049,15 @@ xfs_vm_writepage(
|
||||||
/*
|
/*
|
||||||
* Refuse to write the page out if we are called from reclaim context.
|
* Refuse to write the page out if we are called from reclaim context.
|
||||||
*
|
*
|
||||||
* This is primarily to avoid stack overflows when called from deep
|
* This avoids stack overflows when called from deeply used stacks in
|
||||||
* used stacks in random callers for direct reclaim, but disabling
|
* random callers for direct reclaim or memcg reclaim. We explicitly
|
||||||
* reclaim for kswap is a nice side-effect as kswapd causes rather
|
* allow reclaim from kswapd as the stack usage there is relatively low.
|
||||||
* suboptimal I/O patters, too.
|
|
||||||
*
|
*
|
||||||
* This should really be done by the core VM, but until that happens
|
* This should really be done by the core VM, but until that happens
|
||||||
* filesystems like XFS, btrfs and ext4 have to take care of this
|
* filesystems like XFS, btrfs and ext4 have to take care of this
|
||||||
* by themselves.
|
* by themselves.
|
||||||
*/
|
*/
|
||||||
if (current->flags & PF_MEMALLOC)
|
if ((current->flags & (PF_MEMALLOC|PF_KSWAPD)) == PF_MEMALLOC)
|
||||||
goto out_fail;
|
goto out_fail;
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|
|
Loading…
Reference in New Issue