public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dirk Brandewie <dirk.j.brandewie@intel.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: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks
Date: Wed, 19 Feb 2014 14:47:52 -0800	[thread overview]
Message-ID: <20140219224752.GA370@kroah.com> (raw)

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?

Oh, and because of the problems, I'll just drop this patch from the
-stable trees for now, I don't want to pollute them with the issue until
it is resolved properly.

thanks,

greg k-h

             reply	other threads:[~2014-02-19 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 22:47 Greg KH [this message]
2014-02-20  0:03 ` Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks Dirk Brandewie
2014-02-20  0:35   ` Greg KH
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=20140219224752.GA370@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.j.brandewie@intel.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