From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757223Ab0JUCki (ORCPT ); Wed, 20 Oct 2010 22:40:38 -0400 Received: from mail.digidescorp.com ([66.244.163.200]:28156 "EHLO digidescorp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757042Ab0JUCkh (ORCPT ); Wed, 20 Oct 2010 22:40:37 -0400 X-Greylist: delayed 314 seconds by postgrey-1.27 at vger.kernel.org; Wed, 20 Oct 2010 22:40:36 EDT X-Spam-Processed: digidescorp.com, Wed, 20 Oct 2010 21:35:20 -0500 (not processed: message was sent from localhost) X-Authenticated-Sender: steve@digidescorp.com X-Return-Path: prvs=191030265f=steve@digidescorp.com X-Envelope-From: steve@digidescorp.com X-MDaemon-Deliver-To: linux-kernel@vger.kernel.org Date: Wed, 20 Oct 2010 21:35:16 -0500 From: "Steve Magnani" To: "KAMEZAWA Hiroyuki" Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org, dhowells@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH V2] nommu: add anonymous page memcg accounting MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: X-Mailer: WorldClient 10.1.1 In-Reply-To: <20101021090847.b4e23dde.kamezawa.hiroyu@jp.fujitsu.com> References: <1287491654-4005-1-git-send-email-steve@digidescorp.com> <20101019154819.GC15844@balbir.in.ibm.com> <1287512657.2500.31.camel@iscandar.digidescorp.com> <20101020091746.f0cc5dc2.kamezawa.hiroyu@jp.fujitsu.com> <1287578957.2603.34.camel@iscandar.digidescorp.com> <20101021090847.b4e23dde.kamezawa.hiroyu@jp.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-10-21 at 09:08 +0900, KAMEZAWA Hiroyuki wrote: > I myself can't maintain NOMMU kernel. So, please test every -rc1 when > this patch merged. OK ? It's reasonable to ask that features be tested every so often, and since the memory cgroup code seems to be changing relatively frequently it probably needs exercising more often. I can't commit to this, though - I don't know how much longer I'll be working with NOMMU kernels, and they are notoriously fragile. Any memory access bug that would cause an oops (or SEGV) in a "normal" kernel can cause subtle and almost impossible to debug behavior on a NOMMU system. For this reason I always try to work with "stable" kernels (recent threads debating the term notwithstanding)...so it would be a pretty far jump to a -rc1 kernel. Is this a showstopper (in which case David's patch to make the CGROUP_MEM_RES_CTLR Kconfig option depend on MMU should be implemented), or should I post V3 of the patch that has Balbir's suggested change? Steve