Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759463AbZLJCVU (ORCPT ); Wed, 9 Dec 2009 21:21:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759213AbZLJCVS (ORCPT ); Wed, 9 Dec 2009 21:21:18 -0500 Received: from e23smtp06.au.ibm.com ([202.81.31.148]:56905 "EHLO e23smtp06.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759207AbZLJCVR (ORCPT ); Wed, 9 Dec 2009 21:21:17 -0500 Date: Thu, 10 Dec 2009 07:51:13 +0530 From: Balbir Singh To: Andi Kleen Cc: Paul Menage , kosaki.motohiro@jp.fujitsu.com, hugh.dickins@tiscali.co.uk, nishimura@mxp.nes.nec.co.jp, kamezawa.hiroyu@jp.fujitsu.com, lizf@cn.fujitsu.com, npiggin@suse.de, fengguang.wu@intel.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH] [23/31] HWPOISON: add memory cgroup filter Message-ID: <20091210022113.GJ3722@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com References: <200912081016.198135742@firstfloor.org> <20091208211639.8499FB151F@basil.firstfloor.org> <6599ad830912091247v1270a86er45ea8ceeff28e727@mail.gmail.com> <20091210014212.GI18989@one.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20091210014212.GI18989@one.firstfloor.org> User-Agent: Mutt/1.5.20 (2009-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1323 Lines: 32 * Andi Kleen [2009-12-10 02:42:12]: > > While the functionality sounds useful, the interface (passing an inode > > number) feels a bit ugly to me. Also, if that group is deleted and a > > new cgroup created, you could end up reusing the inode number. > > Please note this is just a testing interface, doesn't need to be > 100% fool-proof. It'll never be used in production. > > > > > How about an approach where you write either the cgroup path (relative > > to the memcg mount) or an fd open on the desired cgroup? Then you > > could store a (counted) css reference rather than an inode number, > > which would make the filter function cleaner too, since it would just > > need to compare css objects. > > Sounds complicated, I assume it would be much more code? > I would prefer to keep the testing interfaces as simple as possible. > We do this for cgroupstats and the code is not very complicated. In case you want to look, the user space code is at Documentation/accounting/getdelays.c and the kernel code is in kernel/taskstats.c -- 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/