| To: | Mel Gorman <mgorman@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 8/8] mm: vmscan: Do not writeback filesystem pages from kswapd |
| From: | Peter Zijlstra <peterz@xxxxxxxxxxxxx> |
| Date: | Fri, 22 Jul 2011 14:57:12 +0200 |
| Cc: | Linux-MM <linux-mm@xxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, XFS <xfs@xxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Johannes Weiner <jweiner@xxxxxxxxxx>, Wu Fengguang <fengguang.wu@xxxxxxxxx>, Jan Kara <jack@xxxxxxx>, Rik van Riel <riel@xxxxxxxxxx>, Minchan Kim <minchan.kim@xxxxxxxxx> |
| In-reply-to: | <1311265730-5324-9-git-send-email-mgorman@xxxxxxx> |
| References: | <1311265730-5324-1-git-send-email-mgorman@xxxxxxx> <1311265730-5324-9-git-send-email-mgorman@xxxxxxx> |
On Thu, 2011-07-21 at 17:28 +0100, Mel Gorman wrote: > Assuming that flusher threads will always write back dirty pages promptly > then it is always faster for reclaimers to wait for flushers. This patch > prevents kswapd writing back any filesystem pages. That is a somewhat sort changelog for such a big assumption ;-) I think it can use a few extra words to explain the need to clean pages from @zone vs writeback picks whatever fits best on disk and how that works out wrt the assumption. What requirements does this place on writeback and how does it meet them. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 7/8] mm: vmscan: Immediately reclaim end-of-LRU dirty pages when writeback completes, Peter Zijlstra |
|---|---|
| Next by Date: | Re: [PATCH 7/8] mm: vmscan: Immediately reclaim end-of-LRU dirty pages when writeback completes, Mel Gorman |
| Previous by Thread: | [PATCH 8/8] mm: vmscan: Do not writeback filesystem pages from kswapd, Mel Gorman |
| Next by Thread: | Re: [PATCH 8/8] mm: vmscan: Do not writeback filesystem pages from kswapd, Mel Gorman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |