From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753768AbbHRSWT (ORCPT ); Tue, 18 Aug 2015 14:22:19 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:34020 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751165AbbHRSWR (ORCPT ); Tue, 18 Aug 2015 14:22:17 -0400 Date: Tue, 18 Aug 2015 21:22:14 +0300 From: "Kirill A. Shutemov" To: Michal Hocko Cc: "Kirill A. Shutemov" , Andrew Morton , Hugh Dickins , Andrea Arcangeli , Dave Hansen , Vlastimil Babka , Johannes Weiner , David Rientjes , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCHv2 3/4] mm: pack compound_dtor and compound_order into one word in struct page Message-ID: <20150818182214.GA21383@node.dhcp.inet.fi> References: <1439824145-25397-1-git-send-email-kirill.shutemov@linux.intel.com> <1439824145-25397-4-git-send-email-kirill.shutemov@linux.intel.com> <20150818154259.GL5033@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150818154259.GL5033@dhcp22.suse.cz> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 18, 2015 at 05:43:00PM +0200, Michal Hocko wrote: > On Mon 17-08-15 18:09:04, Kirill A. Shutemov wrote: > > The patch halves space occupied by compound_dtor and compound_order in > > struct page. > > > > For compound_order, it's trivial long -> int/short conversion. > > > > For get_compound_page_dtor(), we now use hardcoded table for destructor > > lookup and store its index in the struct page instead of direct pointer > > to destructor. It shouldn't be a big trouble to maintain the table: we > > have only two destructor and NULL currently. > > > > This patch free up one word in tail pages for reuse. This is preparation > > for the next patch. > > > > Signed-off-by: Kirill A. Shutemov > > Reviewed-by: Michal Hocko > > [...] > > @@ -145,8 +143,13 @@ struct page { > > */ > > /* First tail page of compound page */ > > struct { > > - compound_page_dtor *compound_dtor; > > - unsigned long compound_order; > > +#ifdef CONFIG_64BIT > > + unsigned int compound_dtor; > > + unsigned int compound_order; > > +#else > > + unsigned short int compound_dtor; > > + unsigned short int compound_order; > > +#endif > > }; > > Why do we need this ifdef? We can go with short for both 32b and 64b > AFAICS. My assumption was that operations on ints can be faster on some [micro]arhictectures. I'm not sure if it's ever true. > We do not use compound_order for anything else than the order, right? Right. > While I am looking at this, it seems we are jugling with type for order > quite a lot - int, unsing int and even unsigned long. Yeah. It's mess. I'll check if I can fix anything of it in v3. -- Kirill A. Shutemov