public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks
Date: Wed, 19 Feb 2014 16:35:37 -0800	[thread overview]
Message-ID: <20140220003537.GA4671@kroah.com> (raw)
In-Reply-To: <5305465C.7060806@gmail.com>

On Wed, Feb 19, 2014 at 04:03:40PM -0800, Dirk Brandewie wrote:
> On 02/19/2014 02:47 PM, Greg KH wrote:
> >Hi Dirk,
> >
> >I've been having some huge slowdowns on my box building kernels, and I
> >took the time to bisect it down to commit
> >fcb6a15c2e7e76d493e6f91ea889ab40e1c643a4 (intel_pstate: Take core C0
> >time into account for core busy calculation).  With that patch reverted
> >on Linus's current tree, my build speeds are back up to the normal rate.
> >
> >The difference is huge, 2 minutes to do a kernel build with that patch
> >reverted, 8-10 minutes with it applied!  With all of the stable kernel
> >builds and other trees, this is a huge problem for my workload (all I do
> >is kernel builds it seems...)
> >
> >I see some patches you marked as "fixes" that you sent to Rafael, do you
> >want me to test any of those?  How am I the only one seeing this
> >problem, do you need my cpu information or anything else?
> 
> Can you give me a description of you build system?  CPU, number of sockets,

The last processor in /proc/cpuinfo:

processor       : 7
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
stepping        : 3
microcode       : 0x9
cpu MHz         : 3556.464
cache size      : 8192 KB
physical id     : 0
siblings        : 8
core id         : 3
cpu cores       : 4
apicid          : 7
initial apicid  : 7
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
bogomips        : 7000.78
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual

> building from/to local media.  Any special setup I should use here for my test?

I build on a SSD-like disk (flash media on PCI Express slot), so I
should have almost no i/o time.

I build with 'make -j16'

> If you have time having the output of turbostat for a build with and
> without would be very useful.

 $ ./turbostat
 turbostat: no /dev/cpu/0/msr
 Try "# modprobe msr": No such file or directory

Bah, I'll rebuild with msr and get you that info...

thanks,

greg k-h

  reply	other threads:[~2014-02-20  0:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 22:47 Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks Greg KH
2014-02-20  0:03 ` Dirk Brandewie
2014-02-20  0:35   ` Greg KH [this message]
2014-02-20  0:51     ` Greg KH
2014-02-20 14:56       ` Dirk Brandewie
2014-02-20 18:10         ` Greg KH
2014-02-24 22:37           ` Greg KH
2014-02-24 23:03             ` Dirk Brandewie
2014-02-25 18:35 ` [PATCH] intel_pstate: Change busy calculation to use fixed point math dirk.brandewie
2014-02-26  0:39   ` Rafael J. Wysocki
2014-02-26 14:57     ` Otto Meier
2014-02-28 22:47   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140220003537.GA4671@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox