[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <468D00FF.6070106@linux.vnet.ibm.com>
Date: Thu, 05 Jul 2007 07:32:31 -0700
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Pavel Emelianov <xemul@...nvz.org>
CC: Kirill Korotaev <dev@...nvz.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Containers <containers@...ts.osdl.org>,
Paul Menage <menage@...gle.com>
Subject: Re: [-mm PATCH 0/7] Memory controller introduction
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
-
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