All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
	Ira Weiny <ira.weiny@intel.com>,
	outreachy@lists.linux.dev
Subject: Re: Introductory message
Date: Wed, 08 Mar 2023 19:40:30 +0100	[thread overview]
Message-ID: <6882066.18pcnM708K@suse> (raw)
In-Reply-To: <6408c23d58ec5_f3f4a294e1@iweiny-mobl.notmuch>

On mercoledì 8 marzo 2023 18:13:33 CET Ira Weiny wrote:
> Julia Lawall wrote:
> > On Wed, 8 Mar 2023, Sumitra Sharma wrote:
> > > Hi I am Sumitra Sharma, an outreachy applicant. This is my first time
> > > applying to outreachy and linux-kernel. I am currently working on
> > > setting up the environment. I observed that building the kernel i.e.
> > > running "make -j2" command itself is taking a lot of time. I would
> > > appreciate some suggestions on it.
> > 
> > I think it would take a lot of time...
> 
> Also:
> 
> -j is an option which chooses how many threads to build in parallel.
> 
> If you have enough cores on your machine you could increase '2' to
> something larger.
> 

Sumitra,

That "something larger" can be calculated with a rule of thumb and then 
adapted to your necessities...

Look at /proc/cpuinfo if you don't know how many cores you have in your 
system...

# cat /proc/cpuinfo | grep processor
processor: 0
processor: 1
processor: 2
processor: 3
processor: 4
processor: 5
processor: 6
processor: 7
processor: 8
processor: 9
processor: 10
processor: 11

The output shows that I'm using a 12 core SMT system (https://
en.wikipedia.org/wiki/Simultaneous_multithreading).

So "-j12" is my usual choice for building a kernel in the host, minus the 
number of SMT cores reserved for running VMs.

Thanks,

Fabio
 




  reply	other threads:[~2023-03-08 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 11:41 Introductory message Sumitra Sharma
2023-03-08 11:49 ` Julia Lawall
2023-03-08 17:13   ` Ira Weiny
2023-03-08 18:40     ` Fabio M. De Francesco [this message]
2023-03-09 16:20       ` Dave Jiang
2023-03-08 15:44 ` Alison Schofield
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  8:26 Introductory Message Olofu Ojoachubione
2023-03-09  9:32 ` Nikolai Kondrashov
2023-03-07  9:47 agabaderrick18
2023-03-07 16:04 ` Alison Schofield

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=6882066.18pcnM708K@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=julia.lawall@inria.fr \
    --cc=outreachy@lists.linux.dev \
    --cc=sumitraartsy@gmail.com \
    /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.