From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751622AbaAQO6Y (ORCPT ); Fri, 17 Jan 2014 09:58:24 -0500 Received: from qmta06.emeryville.ca.mail.comcast.net ([76.96.30.56]:51456 "EHLO qmta06.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752271AbaAQO6U (ORCPT ); Fri, 17 Jan 2014 09:58:20 -0500 Date: Fri, 17 Jan 2014 08:58:17 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@nuc To: Dave Hansen cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, penberg@kernel.org Subject: Re: [RFC][PATCH 5/9] mm: rearrange struct page In-Reply-To: <52D85D33.4080509@sr71.net> Message-ID: References: <20140114180042.C1C33F78@viggo.jf.intel.com> <20140114180055.21691733@viggo.jf.intel.com> <52D85D33.4080509@sr71.net> 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 Thu, 16 Jan 2014, Dave Hansen wrote: > Why does it matter *specifically* that "index shares space with > freelist", or that "mapping shares space with s_mem"? No data is ever > handed off in those fields. If the field is corrupted then one needs to figure out what other ways of using this field exists. If one wants to change the page struct fields then also knowlege about possible interconnections are important.