From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by kanga.kvack.org (Postfix) with ESMTP id 48B4D6B003A for ; Thu, 16 Jan 2014 12:10:13 -0500 (EST) Received: by mail-pa0-f54.google.com with SMTP id fa1so2901784pad.41 for ; Thu, 16 Jan 2014 09:10:12 -0800 (PST) Received: from blackbird.sr71.net (www.sr71.net. [198.145.64.142]) by mx.google.com with ESMTP id e8si7665863pac.24.2014.01.16.09.10.09 for ; Thu, 16 Jan 2014 09:10:10 -0800 (PST) Message-ID: <52D81214.7070608@sr71.net> Date: Thu, 16 Jan 2014 09:08:36 -0800 From: Dave Hansen MIME-Version: 1.0 Subject: Re: [PATCH 0/9] re-shrink 'struct page' when SLUB is on. References: <20140103180147.6566F7C1@viggo.jf.intel.com> <20140103141816.20ef2a24c8adffae040e53dc@linux-foundation.org> <20140106043237.GE696@lge.com> <52D05D90.3060809@sr71.net> <20140110153913.844e84755256afd271371493@linux-foundation.org> <52D0854F.5060102@sr71.net> <20140113014408.GA25900@lge.com> <52D41F52.5020805@sr71.net> <52D5B48D.30006@sr71.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter Cc: Joonsoo Kim , Pekka Enberg , Andrew Morton , "linux-mm@kvack.org" , LKML On 01/16/2014 08:44 AM, Christoph Lameter wrote: > On Tue, 14 Jan 2014, Dave Hansen wrote: > >> On 01/14/2014 12:07 PM, Christoph Lameter wrote: >>> One easy way to shrink struct page is to simply remove the feature. The >>> patchset looked a bit complicated and does many other things. >> >> Sure. There's a clear path if you only care about 'struct page' size, >> or if you only care about making the slub fast path as fast as possible. >> We've got three variables, though: >> >> 1. slub fast path speed > > The fast path does use this_cpu_cmpxchg_double which is something > different from a cmpxchg_double and its not used on struct page. Yeah, I'm confusing the two. I might as well say: "slub speed when touching 'struct page'" >> Arranged in three basic choices: >> >> 1. Big 'struct page', fast, medium complexity code >> 2. Small 'struct page', slow, lowest complexity > > The numbers that I see seem to indicate that a big struct page means slow. This was a really tight loop where the caches are really hot, but it did show the large 'struct page' winning: http://sr71.net/~dave/intel/slub/slub-perf-20140109.png As I said in the earlier description, the paravirt code doing interrupt disabling was what really hurt the two spinlock cases. -- 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