From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752701AbaEHDFQ (ORCPT ); Wed, 7 May 2014 23:05:16 -0400 Received: from mail-pd0-f180.google.com ([209.85.192.180]:57402 "EHLO mail-pd0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751542AbaEHDFN (ORCPT ); Wed, 7 May 2014 23:05:13 -0400 Date: Wed, 7 May 2014 20:05:10 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Andrew Morton , Pekka Enberg cc: Dave Hansen , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Christoph Lameter Subject: Re: [PATCH] mm: slub: fix ALLOC_SLOWPATH stat In-Reply-To: Message-ID: References: <20140106204300.DE79BA86@viggo.jf.intel.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) 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 Tue, 21 Jan 2014, David Rientjes wrote: > On Wed, 8 Jan 2014, David Rientjes wrote: > > > > There used to be only one path out of __slab_alloc(), and > > > ALLOC_SLOWPATH got bumped in that exit path. Now there are two, > > > and a bunch of gotos. ALLOC_SLOWPATH can now get set more than once > > > during a single call to __slab_alloc() which is pretty bogus. > > > Here's the sequence: > > > > > > 1. Enter __slab_alloc(), fall through all the way to the > > > stat(s, ALLOC_SLOWPATH); > > > 2. hit 'if (!freelist)', and bump DEACTIVATE_BYPASS, jump to > > > new_slab (goto #1) > > > 3. Hit 'if (c->partial)', bump CPU_PARTIAL_ALLOC, goto redo > > > (goto #2) > > > 4. Fall through in the same path we did before all the way to > > > stat(s, ALLOC_SLOWPATH) > > > 5. bump ALLOC_REFILL stat, then return > > > > > > Doing this is obviously bogus. It keeps us from being able to > > > accurately compare ALLOC_SLOWPATH vs. ALLOC_FASTPATH. It also > > > means that the total number of allocs always exceeds the total > > > number of frees. > > > > > > This patch moves stat(s, ALLOC_SLOWPATH) to be called from the > > > same place that __slab_alloc() is. This makes it much less > > > likely that ALLOC_SLOWPATH will get botched again in the > > > spaghetti-code inside __slab_alloc(). > > > > > > Signed-off-by: Dave Hansen > > > > Acked-by: David Rientjes > > > > Pekka, are you going to pick this up for linux-next? I think it would be > nice to have for 3.14 for those of us who use the stats. > Ping #2. Pekka or Andrew, would you pick this up for linux-next?