From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: balbir@linux.vnet.ibm.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.osdl.org>,
linux-mm <linux-mm@kvack.org>, Balbir Singh <balbir@in.ibm.com>,
Pavel Emelianov <xemul@sw.ru>, Paul Menage <menage@google.com>,
Kirill Korotaev <dev@sw.ru>,
devel@openvz.org, Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Herbert Poetzl <herbert@13thfloor.at>,
Roy Huang <royhuang9@gmail.com>, Aubrey Li <aubreylee@gmail.com>
Subject: Re: [RFC] mm-controller
Date: Fri, 22 Jun 2007 22:05:19 +0530 [thread overview]
Message-ID: <467BFA47.4050802@linux.vnet.ibm.com> (raw)
In-Reply-To: <1182433855.21117.160.camel@twins>
Peter Zijlstra wrote:
> On Thu, 2007-06-21 at 16:33 +0530, Balbir Singh wrote:
>> Peter Zijlstra wrote:
[snip]
> Not quite sure on 2, from reading the pagecache controller, I got the
> impression that enforcing both limits got you into trouble. Merging the
> limits would rid us of that issue, no?
>
Hi Peter,
Setting both limits in pagecache controller (v4) will work correct in
principle. What I intended in the comment is performance issues and
wrong type of page being reclaimed. We are working on the issues and
will fix them in future versions. You can set any combination of
limits and the reclaim will work to keep the page utilization below
limits.
When RSS limit is hit, ANON pages are pushed to swapcache. We would
need to limit swapcache (using pagecache_limit) to force a write out
to disk.
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.
Thank you for the review and new design proposal.
--Vaidy
[snip]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-22 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 9:32 Peter Zijlstra
2007-06-21 11:03 ` Balbir Singh
2007-06-21 13:50 ` Peter Zijlstra
2007-06-21 17:31 ` Balbir Singh
2007-06-22 2:21 ` Pavel Emelianov
2007-06-22 16:35 ` Vaidyanathan Srinivasan [this message]
2007-06-25 16:22 ` Peter Zijlstra
2007-06-25 18:02 ` Vaidyanathan Srinivasan
2007-06-26 3:01 ` Balbir Singh
2007-06-25 17:35 ` Paul Menage
2007-06-25 17:36 ` Paul Menage
2007-06-25 18:22 ` Vaidyanathan Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467BFA47.4050802@linux.vnet.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aubreylee@gmail.com \
--cc=balbir@in.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=peterz@infradead.org \
--cc=royhuang9@gmail.com \
--cc=xemul@sw.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox