All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jean Delvare <jdelvare@suse.de>, 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, 15 Apr 2014 10:36:50 -0700	[thread overview]
Message-ID: <534D6E32.3020003@infradead.org> (raw)
In-Reply-To: <20140415125413.302d1ce1@endymion.delvare>

On 04/15/2014 03:54 AM, Jean Delvare wrote:
> Hi Greg,
> 
> On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
>> On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
> 
>> I do 'allmodconfig'
>> builds all the time, with over 3000 modules.  The build works just fine
>> on "modern" hardware.
> 
>> 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.
> 
> Electricity isn't free, hardware isn't free, rack slot count is finite
> and server room space is limited over here.
> 
> I don't quite see why we should invest in new hardware to shorten the
> build times, if the same can be achieved with our current hardware
> simply with better configuration files. Plus there is no reason to
> choose between the two. We can have new hardware _and_ better configs
> and improve the build times further :-) So your proposal is off-topic
> to some degree.
> 
> And really, I don't see why I should have to wait for 10 minutes for my
> build to complete if half of that is spent building drivers that will
> never be used. The fact that 10 minutes is "reasonable" is irrelevant.
> 
> Of course, if the Linux Foundation, or you personally, are willing to
> buy me a brand new workstation with more CPU power than I currently
> have, I'll gladly accept. You can also donate your powerful laptop to
> the OBS project, they'll be happy to add it to their build farm ;-)

hey, over here also...
I'd like a new fast laptop that does decent allmodconfig build times.  :)
[e.g., a core i7 cpu and ssd and lots of RAM]

-- 
~Randy

  reply	other threads:[~2014-04-15 17:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 12:53 Hardware dependencies in Kconfig 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 [this message]
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
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=534D6E32.3020003@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.