[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F3D4E34.9060105@fb.com>
Date: Thu, 16 Feb 2012 10:43:00 -0800
From: Arun Sharma <asharma@...com>
To: Andrea Righi <andrea@...terlinux.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan.kim@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Johannes Weiner <jweiner@...hat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Rik van Riel <riel@...hat.com>,
Hugh Dickins <hughd@...gle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Shaohua Li <shaohua.li@...el.com>,
Pádraig Brady <P@...igBrady.com>,
John Stultz <john.stultz@...aro.org>,
Jerry James <jamesjer@...terlinux.com>,
Julius Plenz <julius@...nz.com>, linux-mm <linux-mm@...ck.org>,
<linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 3/3] fadvise: implement POSIX_FADV_NOREUSE
On 2/16/12 2:39 AM, Andrea Righi wrote:
> Arun, thank you very much for your review and testing. Probably we'll
> move to a different, memcg-based solution, so I don't think I'll post
> another version of this patch set as is. In case, I'll apply one of
> the workarounds for the rb_root attribute.
I'm not sure if the proposed memory.file.limit_in_bytes is the right
interface. Two problems:
* The user is now required to figure out what is the right amount of
page cache for the app (may change over time)
* If the app touches two sets of files, one with streaming access and
the other which benefits from page cache (eg: a mapper task in a map
reduce), memcg doesn't allow the user to specify the access pattern per-fd.
-Arun
--
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