From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] add a script to diff rendered documentation
Date: Mon, 6 Aug 2018 12:42:08 -0400 [thread overview]
Message-ID: <20180806164208.GB19053@sigill.intra.peff.net> (raw)
In-Reply-To: <20180806150100.GC97564@aiede.svl.corp.google.com>
On Mon, Aug 06, 2018 at 08:01:00AM -0700, Jonathan Nieder wrote:
> Jeff King wrote:
>
> > 3. Default to number of CPUs, which is what a lot of other threading
> > in Git does. Unfortunately getting that from the shell is
> > non-trivial. I'm OK with $(grep -c ^processor /proc/cpuinfo), but
> > people on non-Linux platforms would have to fill in their own
> > implementation.
>
> How about $(getconf _NPROCESSORS_ONLN)? That's what Linux's
> scripts/coccicheck uses (apropos of a recent discussion :)).
Thanks, that's certainly less gross than grepping /proc/cpuinfo. getconf
is POSIX, but _NPROCESSORS_ONLN is not. According to [1], it works on
Linux and macOS, which is probably a reasonable start, though. This is,
after all, a script aimed at developers, and the worst case is that we
default back to 1.
-Peff
[1] https://stackoverflow.com/questions/42862559/one-liner-for-n-1-cores/42863212#42863212
next prev parent reply other threads:[~2018-08-06 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 20:52 [PATCH] add a script to diff rendered documentation Jeff King
2018-08-03 21:33 ` Eric Sunshine
2018-08-03 21:38 ` Jeff King
2018-08-03 21:44 ` Eric Sunshine
2018-08-03 21:47 ` Junio C Hamano
2018-08-03 22:41 ` Eric Sunshine
2018-08-05 20:49 ` brian m. carlson
2018-08-06 13:39 ` Jeff King
2018-08-06 13:42 ` Jeff King
2018-08-06 15:16 ` Junio C Hamano
2018-08-06 16:57 ` Jeff King
2018-08-06 15:01 ` Jonathan Nieder
2018-08-06 16:42 ` Jeff King [this message]
2018-08-06 17:37 ` Jeff King
2018-08-06 18:25 ` Junio C Hamano
2018-08-06 18:58 ` Jeff King
2018-08-06 19:29 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180806164208.GB19053@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).