[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CE40129.9060103@redhat.com>
Date: Wed, 17 Nov 2010 11:22:01 -0500
From: Rik van Riel <riel@...hat.com>
To: Minchan Kim <minchan.kim@...il.com>
CC: Peter Zijlstra <peterz@...radead.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Ben Gamari <bgamari.foss@...il.com>,
linux-kernel@...r.kernel.org, rsync@...ts.samba.org,
linux-mm@...ck.org, Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: fadvise DONTNEED implementation (or lack thereof)
On 11/17/2010 05:16 AM, Minchan Kim wrote:
> Absolutely. But how about rsync's two touch?
> It can evict working set.
>
> I need the time for investigation.
> Thanks for the comment.
Maybe we could exempt MADV_SEQUENTIAL and FADV_SEQUENTIAL
touches from promoting the page to the active list?
Then we just need to make sure rsync uses fadvise properly
to keep the working set protected from rsync.
--
All rights reversed
--
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