From: Panu Matilainen <pmatilai@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] scripts: support any legal git revisions as abi validation range
Date: Thu, 3 Dec 2015 15:44:29 +0200 [thread overview]
Message-ID: <5660473D.10003@redhat.com> (raw)
In-Reply-To: <2244682.HuU20AYBFi@xps13>
On 12/03/2015 03:28 PM, Thomas Monjalon wrote:
> 2015-12-03 12:14, Mcnamara, John:
>> Also, if someone has some bandwidth it would be good to add an option
>> to pass -j with an optional number to "make" in the script.
>
> We can use -j without any number:
> "make will not limit the number of jobs that can run simultaneously".
> It is a not so bad default.
>
Hmm, my memory associates an unlimited -j to make with sudden death by
fork-bomb. But that was a long time ago and on a different codebase (the
kernel maybe), with DPDK on current hardware it doesn't seem that bad at
all.
OTOH we can also simply ask the system for a reasonable value, eg
$ /usr/bin/getconf _NPROCESSORS_ONLN
- Panu -
next prev parent reply other threads:[~2015-12-03 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 16:50 Panu Matilainen
2015-12-02 18:23 ` Neil Horman
2015-12-03 12:14 ` Mcnamara, John
2015-12-03 13:28 ` Thomas Monjalon
2015-12-03 13:44 ` Panu Matilainen [this message]
2015-12-03 13:49 ` Richardson, Bruce
2015-12-03 15:46 ` Mcnamara, John
2015-12-03 13:39 ` Panu Matilainen
2015-12-03 13:41 ` Thomas Monjalon
2015-12-03 14:05 ` [dpdk-dev] [PATCH v2] " Panu Matilainen
2015-12-07 14:09 ` Panu Matilainen
2015-12-07 14:32 ` Thomas Monjalon
2015-12-07 16:08 ` Panu Matilainen
2015-12-07 22:38 ` Thomas Monjalon
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=5660473D.10003@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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 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).