Messages in this thread Patch in this message | | | From | KOSAKI Motohiro <> | Subject | [PATCH 2/4] vmscan: drop PF_SWAPWRITE from zone_reclaim | Date | Wed, 13 May 2009 12:06:51 +0900 (JST) |
| |
Subject: [PATCH] vmscan: drop PF_SWAPWRITE from zone_reclaim
PF_SWAPWRITE mean ignore write congestion. (see may_write_to_queue())
foreground reclaim shouldn't ignore it because to write congested device cause large IO lantency. it isn't better than remote node allocation.
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Cc: Christoph Lameter <cl@linux-foundation.org> Cc: Rik van Riel <riel@redhat.com> --- mm/vmscan.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Index: b/mm/vmscan.c =================================================================== --- a/mm/vmscan.c +++ b/mm/vmscan.c @@ -2406,7 +2406,7 @@ static int __zone_reclaim(struct zone *z * and we also need to be able to write out pages for RECLAIM_WRITE * and RECLAIM_SWAP. */ - p->flags |= PF_MEMALLOC | PF_SWAPWRITE; + p->flags |= PF_MEMALLOC; reclaim_state.reclaimed_slab = 0; p->reclaim_state = &reclaim_state; @@ -2453,7 +2453,7 @@ static int __zone_reclaim(struct zone *z } p->reclaim_state = NULL; - current->flags &= ~(PF_MEMALLOC | PF_SWAPWRITE); + current->flags &= ~PF_MEMALLOC; return sc.nr_reclaimed >= nr_pages; }
| |