Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755863AbcDHAOC (ORCPT ); Thu, 7 Apr 2016 20:14:02 -0400 Received: from mail-oi0-f47.google.com ([209.85.218.47]:33165 "EHLO mail-oi0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751706AbcDHAOA (ORCPT ); Thu, 7 Apr 2016 20:14:00 -0400 MIME-Version: 1.0 In-Reply-To: <570677BD.1000800@hpe.com> References: <1459951324-53339-1-git-send-email-Waiman.Long@hpe.com> <570677BD.1000800@hpe.com> From: Andy Lutomirski Date: Thu, 7 Apr 2016 17:13:40 -0700 Message-ID: Subject: Re: [PATCH] x86/hpet: Reduce HPET counter read contention To: Waiman Long Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , X86 ML , Jiang Liu , Borislav Petkov , Andy Lutomirski , Scott J Norton , Douglas Hatch , Randy Wright Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 859 Lines: 27 On Thu, Apr 7, 2016 at 8:07 AM, Waiman Long wrote: > On 04/07/2016 12:58 AM, Andy Lutomirski wrote: >> Reading the HPET is so slow that all the atomic ops in the world won't >> make a dent. Why not just turn this optimization on unconditionally? >> >> --Andy > > > I am constantly on the alert that we should not introduce regression on > lesser systems like a single socket machine with a few cores. That is why I > put the check to conditionally enable this optimization. I have no issue of > taking that out and let it be the default as long as no one object. > Agreed. I just suspect it's actually faster on all systems. This reminds me -- I need to send out my patch to disable the vdso HPET code, which will make your change more effective. I'll cc you. > Cheers, > Longman -- Andy Lutomirski AMA Capital Management, LLC