LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 24
Date: Mon, 28 May 2018 12:04:35 +0100 [thread overview]
Message-ID: <20180528110435.GA6542@sirena.org.uk> (raw)
In-Reply-To: <CAK8P3a2vmbxYmMqTYb0kHoB3uTcWi_=hL=Wunfw6nqE0NGr+QA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Mon, May 28, 2018 at 11:08:22AM +0200, Arnd Bergmann wrote:
> One possible reason for slowdown on ARM allmodconfig might be the addition of
> KCOV, though that is only enabled in mmotm at the end of your builds.
It's not that - it's slow on just the main builds (x86 allmodconfig, arm
multi_v7_defconfig and arm64 defconfig when I'm doing it). I think it's
due to a combination of some degree of natural growth in build size and
the builds now all being forked off at once rather than being run
sequentially - the system ends up either context thrashing at the start
of the build or using too few cores for the allmodconfig but I was too
busy running the builds to experiment much.
My system isn't nearly so fancy as Stephen's which probably doesn't help
here, I do keep thinking about upgrading so there's a good chance that
next time I try I'll have done so.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-28 11:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 17:30 Mark Brown
2018-05-27 18:46 ` Mark Brown
2018-05-27 19:20 ` Stephen Rothwell
2018-05-28 9:08 ` Arnd Bergmann
2018-05-28 11:04 ` Mark Brown [this message]
2018-05-28 12:23 ` Andy Shevchenko
2018-05-29 10:38 ` Mark Brown
2018-05-29 11:18 ` Stephen Rothwell
2018-05-29 11:37 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-05-24 9:26 Stephen Rothwell
2021-05-24 6:08 Stephen Rothwell
2019-05-24 4:07 Stephen Rothwell
2017-05-24 3:23 Stephen Rothwell
2016-05-24 2:43 Stephen Rothwell
2012-05-24 6:49 Stephen Rothwell
2011-05-24 4:02 Stephen Rothwell
2010-05-24 3:57 Stephen Rothwell
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=20180528110435.GA6542@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--subject='Re: linux-next: Tree for May 24' \
/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
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).