From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764285AbYEBB3L (ORCPT ); Thu, 1 May 2008 21:29:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754785AbYEBB26 (ORCPT ); Thu, 1 May 2008 21:28:58 -0400 Received: from relay1.sgi.com ([192.48.171.29]:51504 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750963AbYEBB25 (ORCPT ); Thu, 1 May 2008 21:28:57 -0400 Date: Thu, 1 May 2008 18:28:57 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Nick Piggin cc: "Ahmed S. Darwish" , Linux Memory Management List , Linux Kernel Mailing List Subject: Re: [patch] SLQB v2 In-Reply-To: <20080502012321.GE30768@wotan.suse.de> Message-ID: References: <20080410193137.GB9482@wotan.suse.de> <20080415034407.GA9120@ubuntu> <20080501015418.GC15179@wotan.suse.de> <20080502004325.GA30768@wotan.suse.de> <20080502012321.GE30768@wotan.suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2 May 2008, Nick Piggin wrote: > But overloading struct page values happens in other places too. Putting > everything into struct page is not scalable. We could also make kmalloc Well lets at least attempt to catch the biggest users. Also makes code clearer if you f.e. use page->first_page instead of page->private for compound pages. kmalloc is intended to return an arbitrary type. struct page has a defined format that needs to be respected.