From: Pratyush Das <reikdas@gmail.com>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: "Enzo Desiage" <enzo@desiage.org>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: .config
Date: Sun, 23 Feb 2020 12:17:14 +0530 [thread overview]
Message-ID: <CAFzLTsmzEdAZRYA5ApF2UpfWcuYosZaCdqrw9=fhKW7Ou7DWqg@mail.gmail.com> (raw)
In-Reply-To: <CAFSeFg_y4h2X-sGebUvjCHqD9E42Br-xE=boGWbdtZ3VtRvpuQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
>
> Next time try make -j<number of cpu cores + 1 )
I thought it was limited by the number of processor threads? In this case,
if each CPU core has just one thread, the +1 does not really serve a
purpose?
Cheers,
On Sun, 23 Feb 2020 at 09:26, Aruna Hewapathirane <
aruna.hewapathirane@gmail.com> wrote:
> >> On Sat, Feb 22, 2020 at 12:39 PM Enzo Desiage <enzo@desiage.org> wrote
> >> Thanks, it worked!
>
> Next time try make -j<number of cpu cores + 1 ) , that is lets say you
> have two cores ?
>
> make -j3
>
> usually will cut down compile time in half :-)
>
> Aruna
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Pratyush Das(Reik)
[-- Attachment #1.2: Type: text/html, Size: 1832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-23 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:41 .config Enzo Desiage
2020-02-22 0:15 ` .config Valdis Klētnieks
2020-02-22 17:39 ` .config Enzo Desiage
2020-02-22 22:47 ` .config Valdis Klētnieks
2020-02-23 3:54 ` .config Aruna Hewapathirane
2020-02-23 6:47 ` Pratyush Das [this message]
2020-02-23 12:18 ` .config Bjørn Mork
2020-02-23 7:31 ` .config Greg KH
2020-02-23 16:29 ` .config Enzo Desiage
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='CAFzLTsmzEdAZRYA5ApF2UpfWcuYosZaCdqrw9=fhKW7Ou7DWqg@mail.gmail.com' \
--to=reikdas@gmail.com \
--cc=aruna.hewapathirane@gmail.com \
--cc=enzo@desiage.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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.