mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörg Otte" <jrg.otte@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Michal Marek <mmarek@suse.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Ming Lei <tom.leiming@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [4.9-rc1] Build-time 2x slower
Date: Thu, 20 Oct 2016 09:57:45 +0200	[thread overview]
Message-ID: <CADDKRnDdtRo0R2sxfZBJS7JBFn_uxQfcYACh3_aPRZvWkG2vJQ@mail.gmail.com> (raw)
In-Reply-To: <2198826.9suuMCzPZN@vostro.rjw.lan>

2016-10-19 22:55 GMT+02:00 Rafael J. Wysocki <rjw@rjwysocki.net>:
> On Wednesday, October 19, 2016 06:59:35 PM Jörg Otte wrote:
>> 2016-10-19 17:29 GMT+02:00 Linus Torvalds <torvalds@linux-foundation.org>:
>> > On Wed, Oct 19, 2016 at 4:07 AM, Jörg Otte <jrg.otte@gmail.com> wrote:
>> >>
>> >> Additional info: I usally use schedutil governor.
>> >> If I switch to performance governor problems go away.
>> >> Maybe a cpufreq problem?
>> >
>> > Oh, I completely misread the original bug report, and then didn't read
>> > your confirmation email right.
>> >
>> > I thought you had a slower build of the different kernels (when
>> > building on the same kernel), and that the _build_ itself had slowed
>> > down for some reason. But you're actually saying that doing the _same_
>> > build actually takes longer when running on 4.9-rc1.
>>
>> Exactly!
>>
>> Btw: ondemand governor is also good.
>>
>> > There are a few small cpufreq changes there in between commit
>> > 29fbff8698fc (that you reported was fine - please tell me I got _that_
>> > right, at least?) and 4.9-rc1.
>>
>> Perfect! That's what I mean.
>>
>> > Adding Rafael to the cc.
>> >
>> > That said, none of them look all that likely to me. It *would* be good
>> > if you could bisect it a bit (perhaps not fully, but a couple of
>> > bisection steps to narrow down what area it is).
>>
>> I try that tomorrow.
>
> Well, please try commit ef98988ba369 (Merge tag 'pm-extra-4.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm) which is the
> merge introducing the late cpufreq changes.  If the issue is there, please
> try to revert commit 899bb6642f2a (cpufreq: skip invalid entries when searching
> the frequency) which is the only cpufreq one that may matter for the schedutil
> governor (and I have one fix for that commit queued up already).
>

I first tried the merge but git said I'm already uptodate (my tree
is at 1a1891d Merge tag 'for-f2fs-4.9-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs already)

Then I did the revert of 899bb6642f2a and
that worked fine for me.

Thanks, Jörg

  parent reply	other threads:[~2016-10-20  7:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 16:04 Sedat Dilek
2016-10-17 16:46 ` Linus Torvalds
2016-10-18  9:28   ` Sedat Dilek
2016-10-18  1:38 ` Ming Lei
2016-10-18  9:30   ` Sedat Dilek
2016-10-18 16:49     ` Jörg Otte
2016-10-18 17:19       ` Linus Torvalds
2016-10-19 11:07         ` Jörg Otte
2016-10-19 15:29           ` Linus Torvalds
2016-10-19 16:59             ` Jörg Otte
2016-10-19 20:55               ` Rafael J. Wysocki
2016-10-20  7:41                 ` Sedat Dilek
2016-10-20 11:15                   ` Rafael J. Wysocki
2016-10-20 14:20                     ` Sedat Dilek
2016-10-20 14:32                       ` Rafael J. Wysocki
2016-10-20 14:38                         ` Sedat Dilek
2016-10-20 14:51                           ` Rafael J. Wysocki
2016-10-21  0:52                         ` Sedat Dilek
2016-10-20  7:57                 ` Jörg Otte [this message]
2016-10-20  8:01                   ` Sedat Dilek
2016-10-20 11:14                   ` Rafael J. Wysocki
2016-10-20 14:32                     ` Jörg Otte
2016-10-20 14:53                       ` Rafael J. Wysocki
2016-10-20  7:28               ` Sedat Dilek
2016-10-20  7:49             ` Sedat Dilek

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=CADDKRnDdtRo0R2sxfZBJS7JBFn_uxQfcYACh3_aPRZvWkG2vJQ@mail.gmail.com \
    --to=jrg.otte@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=sedat.dilek@gmail.com \
    --cc=tom.leiming@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®