[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830706251035t37f916dcr5e35e40e3470482c@mail.gmail.com>
Date: Mon, 25 Jun 2007 10:35:26 -0700
From: "Paul Menage" <menage@...gle.com>
To: "Vaidyanathan Srinivasan" <svaidy@...ux.vnet.ibm.com>
Cc: "Peter Zijlstra" <peterz@...radead.org>, balbir@...ux.vnet.ibm.com,
"Linux Kernel" <linux-kernel@...r.kernel.org>,
"Linux Containers" <containers@...ts.osdl.org>,
linux-mm <linux-mm@...ck.org>,
"Balbir Singh" <balbir@...ibm.com>,
"Pavel Emelianov" <xemul@...ru>, "Kirill Korotaev" <dev@...ru>,
devel@...nvz.org, "Andrew Morton" <akpm@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Herbert Poetzl" <herbert@...hfloor.at>,
"Roy Huang" <royhuang9@...il.com>,
"Aubrey Li" <aubreylee@...il.com>
Subject: Re: [RFC] mm-controller
On 6/22/07, Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com> wrote:
>
> Merging both limits will eliminate the issue, however we would need
> individual limits for pagecache and RSS for better control. There are
> use cases for pagecache_limit alone without RSS_limit like the case of
> database application using direct IO, backup applications and
> streaming applications that does not make good use of pagecache.
>
If streaming applications would otherwise litter the pagecache with
unwanted data, then limiting their total memory footprint (with a
single limit) and forcing them to drop old data sooner sounds like a
great idea.
Paul
-
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