From: Matthew Wilcox <willy@infradead.org>
To: "Derrick, Jonathan" <jonathan.derrick@intel.com>
Cc: "dhowells@redhat.com" <dhowells@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Parallel compilation performance regression
Date: Thu, 18 Jun 2020 18:05:13 -0700 [thread overview]
Message-ID: <20200619010513.GW8681@bombadil.infradead.org> (raw)
In-Reply-To: <a1bafab884bb60250840a8721b78f4b5d3a6c2ed.camel@intel.com>
On Thu, Jun 18, 2020 at 11:52:55PM +0000, Derrick, Jonathan wrote:
> Hi David,
>
> I've been experiencing a performance regression when running a parallel
> compilation (eg, make -j72) on recent kernels.
I bet you're using a version of make which predates 4.3:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0ddad21d3e99c743a3aa473121dc5561679e26bb
next prev parent reply other threads:[~2020-06-19 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 23:52 Parallel compilation performance regression Derrick, Jonathan
2020-06-19 1:05 ` Matthew Wilcox [this message]
2020-06-19 14:59 ` Derrick, Jonathan
2020-06-20 7:44 ` 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=20200619010513.GW8681@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=dhowells@redhat.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).