From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756740AbaE2H6D (ORCPT ); Thu, 29 May 2014 03:58:03 -0400 Received: from szxga01-in.huawei.com ([119.145.14.64]:31044 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756272AbaE2H6B (ORCPT ); Thu, 29 May 2014 03:58:01 -0400 Message-ID: <5386E854.8000206@huawei.com> Date: Thu, 29 May 2014 15:57:08 +0800 From: Libo Chen User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Thomas Gleixner CC: Mike Galbraith , , LKML , Greg KH , "Li Zefan" , , Huang Qiang Subject: Re: balance storm References: <5382AF2E.1040407@huawei.com> <1401081082.5339.41.camel@marge.simpson.net> <538330B7.5070503@huawei.com> <1401113960.23186.41.camel@marge.simpson.net> <53844510.1040502@huawei.com> <1401184553.5134.115.camel@marge.simpson.net> <53848A2C.5010209@huawei.com> <1401196807.5134.132.camel@marge.simpson.net> <53853604.50500@huawei.com> <1401242038.4721.14.camel@marge.simpson.net> <5385881D.4090601@huawei.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.22.241] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2014/5/28 17:08, Thomas Gleixner wrote: > On Wed, 28 May 2014, Libo Chen wrote: > >> On 2014/5/28 9:53, Mike Galbraith wrote: >>> On Wed, 2014-05-28 at 09:04 +0800, Libo Chen wrote: >>> >>>> oh yes, no tsc only hpet in my box. >>> >>> Making poor E5-2658 box a crippled wreck. >> >> yes,it is. But cpu usage will be down from 15% to 5% when binding >> cpu, so maybe read_hpet is not the root cause. > > Definitely hpet _IS_ the root cause on a machine as large as this, > simply because everything gets serialized on the hpet access. > > Binding stuff to cpus just makes the timing behaviour different, so > the hpet serialization is not that prominent, but still bad enough. > > Talk to your HW/BIOS vendor. The kernel cannot do anything about > defunct hardware. I got it! thanks, Libo > > Thanks, > > tglx > -- > 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/ > >