Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753584Ab2BXCZG (ORCPT ); Thu, 23 Feb 2012 21:25:06 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6787 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752055Ab2BXCZE (ORCPT ); Thu, 23 Feb 2012 21:25:04 -0500 Date: Thu, 23 Feb 2012 21:25:13 -0500 From: Jason Baron To: Mathieu Desnoyers , mingo@elte.hu Cc: Linus Torvalds , Paul Mackerras , "H. Peter Anvin" , Steven Rostedt , a.p.zijlstra@chello.nl, davem@davemloft.net, ddaney.cavm@gmail.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/10] jump label: introduce very_[un]likely + cleanups + docs Message-ID: <20120224022512.GA3777@redhat.com> References: <20120222073251.GB17291@elte.hu> <20120222075334.GA25053@elte.hu> <7479958c-1932-4ced-a7a4-53ac6ea3a38e@email.android.com> <20120222081855.GB25318@elte.hu> <20120222213343.GA19758@bloggs.ozlabs.ibm.com> <20120223100205.GD24310@elte.hu> <20120223223348.GA25513@elte.hu> <20120223223933.GA7942@elte.hu> <20120223231842.GA31030@Krystal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120223231842.GA31030@Krystal> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2281 Lines: 71 On Thu, Feb 23, 2012 at 06:18:42PM -0500, Mathieu Desnoyers wrote: > * Ingo Molnar (mingo@elte.hu) wrote: > > > > * Ingo Molnar wrote: > > > > > So, a modified scheme would be: > > > > > > #include > > > > > > struct static_key key = STATIC_KEY_INIT_TRUE; > > > > > > if (static_key_false(&key)) > > > do unlikely code > > > else > > > do likely code > > > > > > Or: > > > > > > if (static_key_true(&key)) > > > do likely code > > > else > > > do unlikely code > > > > > > The static key is modified via: > > > > > > static_key_slow_inc(&key); > > > ... > > > static_key_slow_dec(&key); > > > > > > Is that API fine? I'll rework the series to such an effect if > > > everyone agrees. > > > > I.e. something like the patch below on top of > > tip:perf/jump-labels. > > > > Untested - will test it and will refactor the series if > > everyone's happy. > > Hi Ingo, > > Reading your documentation updates makes me realise that adding the > "inline" keyword in there would make the whole thing even clearer: > > struct static_key key = STATIC_KEY_INLINE_TRUE_INIT; > struct static_key key = STATIC_KEY_INLINE_FALSE_INIT; > > static_key_inline_true() / static_key_inline_false() > > to show that the "true/false" in there does not mean that the key will > always be true or false (the key value can indeed by changed by calling > static_key_slow_inc/dec), but that the inlined path is either the true > of false branch. > Also, as part of the API, there is a test to check the branch direction - which was 'jump_label_true(key)', but is now also 'static_key_true(key)', so we are going to have to change either the branch site or the test for true/false name. The above 'static_key_inline_true/false' solves that. Also, I do like having a consistent 'static_key_*' prefix for the entire API - definitely an improvement for me. Thanks, -Jason -- 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/