DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:
	mime-version:content-type:content-transfer-encoding:
	content-disposition:references;
	b=U17OV/kkAEDxlkG7vLuspW6Z7ocFcxfkcYLbzakPyUPMnS5FOJ/142hPJyfKWSgC/
	ynUpBHReBtXEqqj2KO3/w==
Message-ID: <6599ad830701161152q75ff29cdo7306c9b8df5c351b@mail.gmail.com>
Date: Tue, 16 Jan 2007 11:52:13 -0800
From: "Paul Menage" <menage@google.com>
To: "Christoph Lameter" <clameter@sgi.com>
Subject: Re: [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
       "Nick Piggin" <nickpiggin@yahoo.com.au>, linux-mm@kvack.org,
       "Andi Kleen" <ak@suse.de>, "Paul Jackson" <pj@sgi.com>,
       "Dave Chinner" <dgc@sgi.com>
In-Reply-To: <20070116054825.15358.65020.sendpatchset@schroedinger.engr.sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070116054743.15358.77287.sendpatchset@schroedinger.engr.sgi.com>
	 <20070116054825.15358.65020.sendpatchset@schroedinger.engr.sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 771
Lines: 17

On 1/15/07, Christoph Lameter <clameter@sgi.com> wrote:
>
> This solution may be a bit hokey. I tried other approaches but this
> one seemed to be the simplest with the least complications. Maybe someone
> else can come up with a better solution?

How about a 64-bit field in struct inode that's used as a bitmask if
there are no more than 64 nodes, and a pointer to a bitmask if there
are more than 64 nodes. The filesystems wouldn't need to be involved
then, as the bitmap allocation could be done in the generic code.

Paul
-
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/