Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752364AbZL1KRq (ORCPT ); Mon, 28 Dec 2009 05:17:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751788AbZL1KRp (ORCPT ); Mon, 28 Dec 2009 05:17:45 -0500 Received: from casper.infradead.org ([85.118.1.10]:45790 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750988AbZL1KRo (ORCPT ); Mon, 28 Dec 2009 05:17:44 -0500 Subject: Re: [PATCH] perf lock: Implement basic sorting function of perf lock From: Peter Zijlstra To: Hitoshi Mitake Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Paul Mackerras , Frederic Weisbecker In-Reply-To: <1261277805-27023-1-git-send-email-mitake@dcl.info.waseda.ac.jp> References: <1261277805-27023-1-git-send-email-mitake@dcl.info.waseda.ac.jp> Content-Type: text/plain; charset="UTF-8" Date: Mon, 28 Dec 2009 11:17:17 +0100 Message-ID: <1261995437.7135.54.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 641 Lines: 14 On Sun, 2009-12-20 at 11:56 +0900, Hitoshi Mitake wrote: > +/* based on kernel/lockdep.c */ > +#define MAX_LOCKDEP_KEYS_BITS 13 > +#define LOCKHASH_BITS (MAX_LOCKDEP_KEYS_BITS - 1) > +#define LOCKHASH_SIZE (1UL << LOCKHASH_BITS) Since you're hashing something fundamentally different than lockdep does I don't think it makes sense to carry either the name or the size along. -- 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/