From: Peter Zijlstra <peterz@infradead.org>
To: Pavel Emelianov <xemul@openvz.org>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@osdl.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
Paul Menage <menage@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kirill Korotaev <dev@openvz.org>
Subject: Re: [-mm PATCH 0/7] Memory controller introduction
Date: Fri, 06 Jul 2007 15:14:50 +0200 [thread overview]
Message-ID: <1183727690.7054.104.camel@twins> (raw)
In-Reply-To: <468CB658.7000204@openvz.org>
On Thu, 2007-07-05 at 13:14 +0400, Pavel Emelianov wrote:
> Separate limits for RSS and RSS+pagecache are also a must.
This I still disagree upon. Page-cache limits are orthogonal to
containers and not a requirement for containers. If you want such a
feature get it in Linux proper and don't sneak it in the backdoor via
containers.
next prev parent reply other threads:[~2007-07-06 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 22:21 [-mm PATCH 0/7] Memory controller introduction Balbir Singh
2007-07-04 22:21 ` [-mm PATCH 1/7] Memory controller resource counters Balbir Singh
2007-07-04 22:21 ` [-mm PATCH 2/7] Memory controller containers setup Balbir Singh
2007-07-04 22:21 ` [-mm PATCH 3/7] Memory controller accounting setup Balbir Singh
2007-07-04 22:22 ` [-mm PATCH 4/7] Memory controller memory accounting Balbir Singh
2007-07-05 18:46 ` Vaidyanathan Srinivasan
2007-07-05 20:03 ` Balbir Singh
2007-07-04 22:22 ` [-mm PATCH 5/7] Memory controller task migration Balbir Singh
2007-07-04 22:22 ` [-mm PATCH 6/7] Memory controller add per container LRU and reclaim Balbir Singh
2007-07-04 22:22 ` [-mm PATCH 7/7] Memory controller OOM handling Balbir Singh
2007-07-05 9:14 ` [-mm PATCH 0/7] Memory controller introduction Pavel Emelianov
2007-07-05 14:32 ` Balbir Singh
2007-07-06 13:14 ` Peter Zijlstra [this message]
2007-07-06 14:06 ` Pavel Emelianov
2007-07-06 15:34 ` Balbir Singh
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=1183727690.7054.104.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@osdl.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dev@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/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