From: Jean Delvare <jdelvare@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
Josh Boyer <jwboyer@fedoraproject.org>
Subject: Re: Hardware dependencies in Kconfig
Date: Tue, 22 Apr 2014 15:42:25 +0200 [thread overview]
Message-ID: <20140422154225.759880c5@endymion.delvare> (raw)
In-Reply-To: <20140415045214.GA32541@kroah.com>
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
> I'd argue that your build systems need to get faster, the laptop I'm
> typing this on can do a full modconfig build, with over 3000 modules, in
> around 20 minutes. My build server in the cloud can do that in less
> than 5 minutes, and that's not a very fast machine these days.
For the record, and again underlining that this isn't the problem I was
discussing originally: an allmodconfig build on my workstation takes a
over 38 minutes. This is a Xeon 5520 CPU (4 cores + HT) and I'm
building on an SSD. The machine is otherwise idle. While this isn't
exactly brand new hardware, it is still reasonably powerful, and 38
minutes is time, especially when you're waiting for the build to
complete before you can resume working on something.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-04-22 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 12:53 Jean Delvare
2014-04-14 13:06 ` Josh Boyer
2014-04-14 19:11 ` Greg KH
2014-04-14 19:59 ` Josh Boyer
2014-04-15 4:53 ` Greg KH
2014-04-15 7:27 ` Jean Delvare
2014-04-14 21:12 ` Jean Delvare
2014-04-15 4:52 ` Greg KH
2014-04-15 10:26 ` Michal Marek
2014-04-15 10:54 ` Jean Delvare
2014-04-15 17:36 ` Randy Dunlap
2014-04-15 11:50 ` Josh Boyer
2014-04-15 15:24 ` Greg KH
2014-04-15 15:34 ` Josh Boyer
2014-04-22 13:42 ` Jean Delvare [this message]
2014-04-29 9:23 ` Pavel Machek
2014-04-23 17:45 ` Generating .config from device tree [was Re: Hardware dependencies in Kconfig] Pavel Machek
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=20140422154225.759880c5@endymion.delvare \
--to=jdelvare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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®