linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: dave.bueso@gmail.com
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: Add build speed up tip in BUILD section.
Date: Sun, 13 Jun 2010 15:18:07 +0200	[thread overview]
Message-ID: <4C14DA8F.9050109@example.com> (raw)
In-Reply-To: <1276434639.16577.6.camel@cowboy>

On 13.06.2010 15:10, Davidlohr Bueso wrote:
> Hi,
>
> IMHO the README file could benefit from GNU make's -j[N] option in BUILD section, as a general tip for users.
>
> Not entirely sure who deals with this file, so sending to Linus.
>
> Thanks.
>
> Signed-off-by: Davidlohr Bueso<dave@gnu.org>
> ---
>   README |    5 +++++
>   1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/README b/README
> index 737838f..fda7d52 100644
> --- a/README
> +++ b/README
> @@ -154,6 +154,11 @@ BUILD directory for the kernel:
>      Please note: If the 'O=output/dir' option is used then it must be
>      used for all invocations of make.
>
> +   Depending on the system and configuration, building the kernel can
> +   take some time. To speed things up you can use GNU make's -j[N] option
> +   to specify the number of jobs to run simultaneously. The N value should
> +   be twice the amount of the machine's CPUs.

I thought not CPUs but cores.

-- 
Janusz Korwin-Mikke:
"Idiota z dyplomem to taki sam idiota,
jak przedtem - tylko z pretensjami."
NP: Jeff Beck - Hip-Notica
NB: 2.6.35-rc3

      reply	other threads:[~2010-06-13 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 13:10 [PATCH] README: Add build speed up tip in BUILD section Davidlohr Bueso
2010-06-13 13:18 ` Piotr Hosowicz [this message]

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=4C14DA8F.9050109@example.com \
    --to=piotr@hosowicz.com \
    --cc=dave.bueso@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).