Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751246AbaLQPgQ (ORCPT ); Wed, 17 Dec 2014 10:36:16 -0500 Received: from resqmta-po-03v.sys.comcast.net ([96.114.154.162]:38558 "EHLO resqmta-po-03v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751138AbaLQPgP (ORCPT ); Wed, 17 Dec 2014 10:36:15 -0500 Date: Wed, 17 Dec 2014 09:36:13 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Joonsoo Kim cc: Joonsoo Kim , akpm@linuxfoundation.org, Steven Rostedt , LKML , Thomas Gleixner , Linux Memory Management List , Pekka Enberg , Jesper Dangaard Brouer Subject: Re: [PATCH 0/7] slub: Fastpath optimization (especially for RT) V1 In-Reply-To: Message-ID: References: <20141210163017.092096069@linux.com> <20141215075933.GD4898@js1304-P5Q-DELUXE> 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 Wed, 17 Dec 2014, Joonsoo Kim wrote: > Ping... and I found another way to remove preempt_disable/enable > without complex changes. > > What we want to ensure is getting tid and kmem_cache_cpu > on the same cpu. We can achieve that goal with below condition loop. > > I ran Jesper's benchmark and saw 3~5% win in a fast-path loop over > kmem_cache_alloc+free in CONFIG_PREEMPT. > > 14.5 ns -> 13.8 ns > > See following patch. Good idea. How does this affect the !CONFIG_PREEMPT case? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/