From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 kernel install bug
Date: Wed, 8 Sep 2010 08:58:03 +0200 [thread overview]
Message-ID: <20100908085803.43e15ec4@surf> (raw)
In-Reply-To: <op.vipbghh4sev97k@joachim-lappis>
Hello,
On Wed, 08 Sep 2010 08:39:43 +0200
"Joachim Pihl" <joachim.pihl@sensordevelopments.com> wrote:
> I think getting virtualbox to use more than one core for the VM will
> probably help even more, but disk access is probably another killer.
> I'll see what I can get virtualbox to do, but I am running a laptop,
> so adding another HD is not an option. Repartitioning is also a mess,
> but it could work.
Well, typically the compilation process is also quite I/O intensive, as
it needs to read and write many, many small files. So bringing more and
more CPU power without bringing the corresponding I/O performance will
not yield significant improvements.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-08 6:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 11:54 [Buildroot] AVR32 kernel install bug Joachim Pihl
2010-09-07 13:09 ` Thomas Petazzoni
2010-09-07 13:19 ` Joachim Pihl
2010-09-07 14:56 ` Thomas Petazzoni
2010-09-08 5:31 ` Joachim Pihl
2010-09-08 6:20 ` Thomas Petazzoni
2010-09-08 6:34 ` Paul Jones
2010-09-08 6:39 ` Joachim Pihl
2010-09-08 6:58 ` Thomas Petazzoni [this message]
2010-09-10 6:40 ` Joachim Pihl
2010-09-10 11:09 ` Joachim Pihl
2010-09-10 14:15 ` Thomas Petazzoni
2010-09-13 5:36 ` Joachim Pihl
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=20100908085803.43e15ec4@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.