From: Greg KH <greg@kroah.com>
To: Harsh chopra <serviceprovider.tester@gmail.com>
Cc: Suraj Upadhyay <usuraj35@gmail.com>, kernelnewbies@kernelnewbies.org
Subject: Re: Computing resources required for kernel development
Date: Sun, 31 May 2020 08:29:08 +0200 [thread overview]
Message-ID: <20200531062908.GA1082896@kroah.com> (raw)
In-Reply-To: <CAPEbqj55MfRz07z+BL6TiFwQu18cL2nbipg+obGTM0_a89Y6JA@mail.gmail.com>
On Sun, May 31, 2020 at 11:42:16AM +0530, Harsh chopra wrote:
> I used
> make -j2 all
The number for -j should be at least the number of cores/cpus in your
system, and usually double works well. I use -j10 for my tiny laptop
and that runs quite nicely.
I suggest running the kcbench tool to get a sense of how fast your
machine is, and what the best -j number is for your system:
https://gitlab.com/knurd42/kcbench.git
Also, don't build the "full" kernel, only build what you need for your
hardware + whatever driver/code you are working on. Read up on the
'make localmodconfig' kernel build option to have it create a
configuration file that is _MUCH_ smaller than all options, which will
make the build times very quick.
Good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-05-31 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 15:26 Computing resources required for kernel development Harsh chopra
2020-05-30 18:44 ` Suraj Upadhyay
2020-05-31 6:12 ` Harsh chopra
2020-05-31 6:29 ` Greg KH [this message]
2020-05-31 8:16 ` Valdis Klētnieks
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=20200531062908.GA1082896@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=serviceprovider.tester@gmail.com \
--cc=usuraj35@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.