From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) by kanga.kvack.org (Postfix) with ESMTP id 6695B6B006E for ; Fri, 21 Nov 2014 07:02:01 -0500 (EST) Received: by mail-la0-f43.google.com with SMTP id q1so4115421lam.16 for ; Fri, 21 Nov 2014 04:01:59 -0800 (PST) Received: from kirsi1.inet.fi (mta-out1.inet.fi. [62.71.2.195]) by mx.google.com with ESMTP id r15si12063120wij.73.2014.11.21.04.01.58 for ; Fri, 21 Nov 2014 04:01:59 -0800 (PST) Date: Fri, 21 Nov 2014 14:01:45 +0200 From: "Kirill A. Shutemov" Subject: Re: [PATCH 06/19] mm: store mapcount for compound page separate Message-ID: <20141121120145.GB16647@node.dhcp.inet.fi> References: <1415198994-15252-1-git-send-email-kirill.shutemov@linux.intel.com> <1415198994-15252-7-git-send-email-kirill.shutemov@linux.intel.com> <546C761D.6050407@redhat.com> <20141119130050.GA29884@node.dhcp.inet.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter , Dave Hansen Cc: Jerome Marchand , "Kirill A. Shutemov" , Andrew Morton , Andrea Arcangeli , Hugh Dickins , Mel Gorman , Rik van Riel , Vlastimil Babka , Naoya Horiguchi , Steve Capper , "Aneesh Kumar K.V" , Johannes Weiner , Michal Hocko , linux-kernel@vger.kernel.org, linux-mm@kvack.org On Thu, Nov 20, 2014 at 02:06:53PM -0600, Christoph Lameter wrote: > On Wed, 19 Nov 2014, Kirill A. Shutemov wrote: > > > I don't think we want to bloat struct page description: nobody outside of > > helpers should use it direcly. And it's exactly what we did to store > > compound page destructor and compound page order. > > This is more like a description what overloading is occurring. Either > add the new way of using it there including a comment explainng things or > please do not overload the field. I can do this although I don't see much value. At least we need to be consistent and do the same for compound destructor and compound order. Dave, you tried to sort mess around struct page recently. Any opinion? BTW, how far we should go there? Should things like PAGE_BUDDY_MAPCOUNT_VALUE and PAGE_BALLOON_MAPCOUNT_VALUE be described in struct page definition too? -- Kirill A. Shutemov -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org