public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Pavel Emelianov <xemul@openvz.org>
Cc: Kirill Korotaev <dev@openvz.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Containers <containers@lists.osdl.org>,
	Paul Menage <menage@google.com>
Subject: Re: [-mm PATCH 0/7] Memory controller introduction
Date: Thu, 05 Jul 2007 07:32:31 -0700	[thread overview]
Message-ID: <468D00FF.6070106@linux.vnet.ibm.com> (raw)
In-Reply-To: <468CB658.7000204@openvz.org>

Hi, Pavel,

Pavel Emelianov wrote:
> Balbir Singh wrote:
> 
> As far as I remember at OLS we decided to implement per-zone RLU
> lists and reuse the lru lock as well. This will remove all the 
> problems with per-container lists inconsistency.
> 

It's there in the TODO list. It is easy to implement. I can do that
in the next revision. We are re-using the LRU lock, since the
isolate_pages callback is called under the zone's LRU lock.

> Separate limits for RSS and RSS+pagecache are also a must.
> 

I remember that we discussed having one limit, but we can come up
with a configuration parameter to do it. I'll do that in the
next release.

> BTW, if you send smb. else's patches you may include a 'From: xxx'
> line into the letter to address the original author.
> 

I'll do that for the res_counters_infra patch. Although I had used
res_counter, the hooks in mm_struct earlier (http://lkml.org/lkml/2007/2/19/12).

A lot of the code for the reclaim logic and the meta_page is yours.
Please do identify patches where you would like to see your
signed-off-by and where you think the entire patch is completely
yours.


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2007-07-05 14:34 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 [this message]
2007-07-06 13:14   ` Peter Zijlstra
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=468D00FF.6070106@linux.vnet.ibm.com \
    --to=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=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