From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755524Ab0IWOFS (ORCPT ); Thu, 23 Sep 2010 10:05:18 -0400 Received: from caiajhbdcaid.dreamhost.com ([208.97.132.83]:51977 "EHLO homiemail-a1.g.dreamhost.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755352Ab0IWOFR (ORCPT ); Thu, 23 Sep 2010 10:05:17 -0400 Subject: Re: [PATCH] kmemleak: add unlikely() optimization to kmemleak_late_init From: Davidlohr Bueso Reply-To: dave@gnu.org To: Catalin Marinas Cc: LKML In-Reply-To: References: <1285089797.2177.2.camel@cowboy> Content-Type: text/plain; charset="UTF-8" Date: Thu, 23 Sep 2010 10:05:12 -0400 Message-ID: <1285250712.2127.1.camel@cowboy> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2010-09-22 at 11:06 +0100, Catalin Marinas wrote: > Davidlohr Bueso wrote: > > kmemleak: add unlikely() optimization to kmemleak_late_init() > > > > Since there it is not very probable that kmemleak_disable() was called right after setting kmemleak_initialized, we could benefit from predicting it. > > The patch is correct and you can add my Acked-by but I don't really > think it's worth. We save ~2 cycles during booting, no-one would ever > notice. > Yeah, it's not a big performance booster, but IMHO it wouldn't hurt to add it. Since you are the maintainer it's up to you if you include it upstream. Thanks, Davidlohr