Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754143Ab0HBSA7 (ORCPT ); Mon, 2 Aug 2010 14:00:59 -0400 Received: from e5.ny.us.ibm.com ([32.97.182.145]:48239 "EHLO e5.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752969Ab0HBSA6 (ORCPT ); Mon, 2 Aug 2010 14:00:58 -0400 Date: Mon, 2 Aug 2010 23:30:51 +0530 From: Balbir Singh To: KAMEZAWA Hiroyuki Cc: Andrew Morton , "linux-mm@kvack.org" , "nishimura@mxp.nes.nec.co.jp" , gthelen@google.com, m-ikeda@ds.jp.nec.com, "linux-kernel@vger.kernel.org" Subject: Re: [RFC][PATCH 1/7][memcg] virtually indexed array library. Message-ID: <20100802180051.GX3863@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com References: <20100727165155.8b458b7f.kamezawa.hiroyu@jp.fujitsu.com> <20100727165303.7d7d18e9.kamezawa.hiroyu@jp.fujitsu.com> <20100728124513.85bfa047.akpm@linux-foundation.org> <20100729093226.7b899930.kamezawa.hiroyu@jp.fujitsu.com> <20100729132703.2d53e8a4.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20100729132703.2d53e8a4.kamezawa.hiroyu@jp.fujitsu.com> User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 39 * KAMEZAWA Hiroyuki [2010-07-29 13:27:03]: > On Thu, 29 Jul 2010 09:32:26 +0900 > KAMEZAWA Hiroyuki wrote: > > > On Wed, 28 Jul 2010 12:45:13 -0700 > > Andrew Morton wrote: > > > > My gut reaction to this sort of thing is "run away in terror". It > > > encourages kernel developers to operate like lackadaisical userspace > > > developers and to assume that underlying code can perform heroic and > > > immortal feats. But it can't. This is the kernel and the kernel is a > > > tough and hostile place and callers should be careful and defensive and > > > take great efforts to minimise the strain they put upon other systems. > > > > > > IOW, can we avoid doing this? > > > > > > > I'll use pre-allocated pointer array in the next version. It's simple even > if a bit slow. > > == > struct mem_cgroup *mem_cgroups[CONFIG_MAX_MEM_CGROUPS] __read_mostly; > #define id_to_memcg(id) mem_cgroups[id]; > == Hmm.. I thought we were going to reuse css_id() and use that to get to the cgroup. May be I am missing something. -- Three Cheers, Balbir -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/