From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <torvalds@linux-foundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: RE: [GIT PULL] pin control bulk changes for v4.16
Date: Mon, 5 Feb 2018 10:09:36 +0000 [thread overview]
Message-ID: <b82adbc32e4444debb947582d3a8291c@AcuMS.aculab.com> (raw)
In-Reply-To: <CA+55aFzMBptQt-QHMR0MM9MA3=1rxcf8ca5qHxrf4Mm0ZobE_A@mail.gmail.com>
From: Linus Torvalds
> Sent: 02 February 2018 22:57
...
> I also wonder if there are any automated tools that try to find these
> kinds of crazy things. I suspect a lot of our build times is the poor
> compiler just reading and parsing header files over and over again,
> and a lot of them are probably not needed.
I've counted system calls during a NetBSD kernel build, I imagine Linux is
much the same.
Most of the calls were open(), and most of those failing opens.
I suspected that most came from searching the -I path to find headers.
Build over NFS and the cost is even more significant (every directory
name in the path (used to) require an NFS message exchange).
David
next prev parent reply other threads:[~2018-02-05 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 13:28 Linus Walleij
2018-02-02 22:56 ` Linus Torvalds
2018-02-03 0:44 ` Linus Torvalds
2018-02-03 0:51 ` Linus Torvalds
2018-02-05 9:20 ` Linus Walleij
2018-02-05 9:27 ` Julia Lawall
2018-02-05 9:42 ` Linus Walleij
2018-02-05 9:58 ` Julia Lawall
2018-02-05 19:08 ` Paul Gortmaker
2018-02-03 10:45 ` Ingo Molnar
2018-02-05 10:09 ` David Laight [this message]
2018-02-05 16:55 ` Linus Torvalds
2018-02-05 17:19 ` Linus Torvalds
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=b82adbc32e4444debb947582d3a8291c@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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
Powered by JetHome