From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 1/3] IMA: move read/write counters into struct inode Date: Wed, 20 Oct 2010 16:38:45 +0200 Message-ID: <20101020143845.GB22271@elte.hu> References: <20101019011650.25346.99614.stgit@paris.rdu.redhat.com> <1287506215.2530.187.camel@localhost.localdomain> <20101019165530.GT19804@ZenIV.linux.org.uk> <1287528546.2530.277.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Al Viro , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, zohar@us.ibm.com, warthog9@kernel.org, david@fromorbit.com, jmorris@namei.org, kyle@mcmartin.ca, hpa@zytor.com, akpm@linux-foundation.org To: Eric Paris Return-path: Content-Disposition: inline In-Reply-To: <1287528546.2530.277.camel@localhost.localdomain> Sender: linux-security-module-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org * Eric Paris wrote: > Executive summary of the day's work: > Yesterday morning: 944 bytes per inode in core > Yesterday night: 24 bytes per inode in core > Tonight: 4 bytes per inode in core. > > That's a x236 time reduction in memory usage. No I didn't even start looking at a > freezer. Which could bring that 4 down to 0, but would add a scalability penalty > on all inodes when IMA was enabled. Why not use inode->i_security intelligently? That already exists so that way it's 0 bytes. Thanks, Ingo