Prev: [PATCH 06/14] vmscan: kill prev_priority completely
Next: [PATCH 04/14] tracing, vmscan: Add trace event when a page is written
From: Mel Gorman on 29 Jun 2010 07:40
As only kswapd and memcg are writing back pages, there should be no
danger of overflowing the stack. Allow the writing back of dirty pages
in xfs from the VM.
Signed-off-by: Mel Gorman <mel(a)csn.ul.ie>
fs/xfs/linux-2.6/xfs_aops.c | 15 ---------------
1 files changed, 0 insertions(+), 15 deletions(-)
diff --git a/fs/xfs/linux-2.6/xfs_aops.c b/fs/xfs/linux-2.6/xfs_aops.c
index 34640d6..4c89db3 100644
@@ -1333,21 +1333,6 @@ xfs_vm_writepage(
trace_xfs_writepage(inode, page, 0);
- * Refuse to write the page out if we are called from reclaim context.
- * This is primarily to avoid stack overflows when called from deep
- * used stacks in random callers for direct reclaim, but disabling
- * reclaim for kswap is a nice side-effect as kswapd causes rather
- * suboptimal I/O patters, too.
- * 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
- * by themselves.
- if (current->flags & PF_MEMALLOC)
- goto out_fail;
* We need a transaction if:
* 1. There are delalloc buffers on the page
* 2. The page is uptodate and we have unmapped buffers
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/