[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110803141807.GA7676@infradead.org>
Date: Wed, 3 Aug 2011 10:18:07 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Johannes Weiner <jweiner@...hat.com>
Cc: Mel Gorman <mgorman@...e.de>, Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>, XFS <xfs@....sgi.com>,
Dave Chinner <david@...morbit.com>,
Christoph Hellwig <hch@...radead.org>,
Wu Fengguang <fengguang.wu@...el.com>, Jan Kara <jack@...e.cz>,
Rik van Riel <riel@...hat.com>,
Minchan Kim <minchan.kim@...il.com>, josef@...hat.com
Subject: Re: [PATCH 3/8] ext4: Warn if direct reclaim tries to writeback pages
On Wed, Aug 03, 2011 at 04:00:19PM +0200, Johannes Weiner wrote:
> > That said, in my current revision of the series, I've dropped these
> > patches altogether as page migration should be able to trigger the same
> > warnings but be called from paths that are of less concern for stack
> > overflows (or at the very least be looked at as a separate series).
>
> Doesn't this only apply to btrfs which has no own .migratepage aop for
> file pages? The others use buffer_migrate_page.
>
> But if you dropped them anyway, it does not matter :)
Note that the mid-term plan is to kill ->writepage as an address space
method. Besides the usage from reclaim as as callbacks to
write_cache_pages and write_one_page (which can be made explicit
arguments) the only remaining user is the above mentioned fallback.
Josef, any chance you could switch btrfs over to implement a proper
->migratepage?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists