From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752836Ab1GVQ1Y (ORCPT ); Fri, 22 Jul 2011 12:27:24 -0400 Received: from mga01.intel.com ([192.55.52.88]:11557 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752314Ab1GVQ1X (ORCPT ); Fri, 22 Jul 2011 12:27:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,248,1309762800"; d="scan'208";a="31239103" From: Andi Kleen To: Jeremy Fitzhardinge Cc: Peter Zijlstra , "H. Peter Anvin" , Ingo Molnar , the arch/x86 maintainers , Linux Kernel Mailing List , Nick Piggin , Jeremy Fitzhardinge Subject: Re: [PATCH RFC 0/7] x86: convert ticketlocks to C and remove duplicate code References: <4E28B749.10304@goop.org> Date: Fri, 22 Jul 2011 09:25:34 -0700 In-Reply-To: <4E28B749.10304@goop.org> (Jeremy Fitzhardinge's message of "Thu, 21 Jul 2011 16:33:29 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) 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 Jeremy Fitzhardinge writes: > > Yes, I observed cases where they were faster. What is your lock > tester? Does it test the lock code in isolation, or in situ? User space harness to test a couple of lock scenarios with different numbers of CPUs competing. It tests the lock code in isolation. -Andi -- ak@linux.intel.com -- Speaking for myself only