From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU updates for v5.1
Date: Tue, 5 Mar 2019 18:13:21 -0800 [thread overview]
Message-ID: <CAHk-=wiM4_0ZDDAcN0nJ8TsK+MnO1ObmSH4nTvrirA5nenFTHA@mail.gmail.com> (raw)
In-Reply-To: <20190305120301.GA93284@gmail.com>
On Tue, Mar 5, 2019 at 4:03 AM Ingo Molnar <mingo@kernel.org> wrote:
>
> Please pull the latest core-rcu-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
Hmm. I think this made my build time explode.
I'm bisecting, but it looks like my allmodconfig builds went from ~31
min to ~39 min with this pull.
NOTE! I'm not saying that the kernel slowed down. Just the *build*
(with the same kernel) slowed down.
It's odd, and maybe I did something wrong, so I'll have to
double-check the numbers, but I thought I'd mention it in case
somebody goes "Ahh, I did X to the include files, so now every
compiler invocation probably sees all of xyz and that will slow things
down enormously".
Linus
next prev parent reply other threads:[~2019-03-06 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 12:03 [GIT PULL] RCU updates for v5.1 Ingo Molnar
2019-03-05 23:15 ` pr-tracker-bot
2019-03-06 2:13 ` Linus Torvalds [this message]
2019-03-06 7:08 ` Ingo Molnar
2019-03-06 14:42 ` Linus Torvalds
2019-03-06 16:32 ` Paul E. McKenney
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='CAHk-=wiM4_0ZDDAcN0nJ8TsK+MnO1ObmSH4nTvrirA5nenFTHA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).