[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1401278112.9793.45.camel@marge.simpson.net>
Date: Wed, 28 May 2014 13:55:12 +0200
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Libo Chen <libo.chen@...wei.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, mingo@...e.hu,
LKML <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>,
Li Zefan <lizefan@...wei.com>, peterz@...radead.org,
Huang Qiang <h.huangqiang@...wei.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: balance storm
On Wed, 2014-05-28 at 19:43 +0800, Libo Chen wrote:
> 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.
>
> thank you for your reply.but suse sp2 is very good in this scene.
> Can it be said there has a bug, then community fix it later,
> so it's just a coincidence?
I'm quite sure it's because of the patches I mentioned.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists