From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757902AbXGDWVp (ORCPT ); Wed, 4 Jul 2007 18:21:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752223AbXGDWVf (ORCPT ); Wed, 4 Jul 2007 18:21:35 -0400 Received: from ausmtp05.au.ibm.com ([202.81.18.154]:60254 "EHLO ausmtp05.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751618AbXGDWVe (ORCPT ); Wed, 4 Jul 2007 18:21:34 -0400 From: Balbir Singh To: Andrew Morton , Vaidyanathan Srinivasan , Pavel Emelianov Cc: Linux Containers , Balbir Singh , Paul Menage , Linux Kernel Mailing List Date: Wed, 04 Jul 2007 15:21:08 -0700 Message-Id: <20070704222108.17702.40293.sendpatchset@balbir-laptop> Subject: [-mm PATCH 0/7] Memory controller introduction Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Resending with the patch numbering fixed and linux-mm copied This patchset implements another version of the memory controller. These patches have been through a big churn, the first set of patches were posted last year and earlier this year at http://lkml.org/lkml/2007/2/19/10 Ever since, the RSS controller has been through four revisions, the latest one being http://lwn.net/Articles/236817/ This patchset draws from the patches listed above and from some of the contents of the patches posted by Vaidyanathan for page cache control. http://lkml.org/lkml/2007/6/20/92 Pavel, Vaidy could you look at the patches and add your signed off by where relevant? At OLS, the resource management BOF, it was discussed that we need to manage RSS and unmapped page cache together. This patchset is a step towards that TODO's 1. Add memory controller water mark support. Reclaim on high water mark 2. Add support for shrinking on limit change 3. Add per zone per container LRU lists 4. Make page_referenced() container aware 5. Figure out a better CLUI for the controller In case you have been using/testing the RSS controller, you'll find that this controller works slower than the RSS controller. The reason being that both swap cache and page cache is accounted for, so pages do go out to swap upon reclaim (they cannot live in the swap cache). I've test compiled the framework without the controller enabled, tested the code on UML and minimally on a power box. Any test output, feedback, comments, suggestions are welcome! series res_counters_infra.patch mem-control-setup.patch mem-control-accounting-setup.patch mem-control-accounting.patch mem-control-task-migration.patch mem-control-lru-and-reclaim.patch mem-control-out-of-memory.patch -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL