From: Campbell Barton <ideasman42@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] support for accessing CPU/core count (processor-count)
Date: Mon, 11 Oct 2021 15:01:38 +1100 [thread overview]
Message-ID: <46728405-9441-4e3d-be5e-75e1bceaee70@gmail.com> (raw)
In-Reply-To: <87sfx8b6ta.fsf@yahoo.com>
On 10/11/21 14:04, Po Lu wrote:
> Campbell Barton <ideasman42@gmail.com> writes:
>
>> This seems like a better location. Updated the patch, including
>> OpenBSD's ncpuonline support from Omar Polo.
>
> Doesn't gnulib already have a portable mechanism to obtain the number of
> CPUs in a system? And if not, wouldn't it be useful there?
Yes, `num_processors (NPROC_ALL)` is an equivalent that would work.
Correction to my previous mail which mentioned CPU affinity being an
issue, that's only used for `NPROC_CURRENT`.
If the additional complexity of GNULib's `lib/nproc.c` isn't viewed as a
major down-side (~279-SLOC ~27-SLOC from the patch I submitted), both
can work.
next prev parent reply other threads:[~2021-10-11 4:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 0:02 [PATCH] support for accessing CPU/core count (processor-count) Campbell Barton
2021-10-10 7:54 ` Omar Polo
2021-10-10 9:38 ` Arthur Miller
2021-10-10 9:43 ` Omar Polo
2021-10-10 10:52 ` Arthur Miller
2021-10-10 12:07 ` Omar Polo
2021-10-10 16:48 ` Arthur Miller
2021-10-10 18:17 ` Omar Polo
2021-10-10 19:45 ` Arthur Miller
2021-10-10 21:04 ` Omar Polo
2021-10-11 8:15 ` Arthur Miller
2021-10-11 8:20 ` Arthur Miller
2021-10-11 8:23 ` Omar Polo
2021-10-11 15:55 ` Arthur Miller
2021-10-10 21:32 ` Andreas Schwab
2021-10-11 8:03 ` Arthur Miller
2021-10-11 8:14 ` Andreas Schwab
2021-10-11 15:53 ` Arthur Miller
2021-10-11 16:49 ` Andreas Schwab
2021-10-11 17:14 ` Arthur Miller
2021-10-10 10:13 ` Campbell Barton
2021-10-10 10:38 ` Andreas Schwab
2021-10-10 11:21 ` Arthur Miller
2021-10-10 11:57 ` Andreas Schwab
2021-10-10 16:35 ` Arthur Miller
2021-10-10 17:27 ` Andreas Schwab
2021-10-10 18:13 ` Arthur Miller
2021-10-10 19:16 ` Stefan Monnier
2021-10-10 19:50 ` Arthur Miller
2021-10-10 22:58 ` Campbell Barton
2021-10-11 8:01 ` Arthur Miller
2021-10-10 12:21 ` Stefan Kangas
2021-10-10 16:03 ` Omar Polo
2021-10-10 21:11 ` Paul Eggert
2021-10-10 21:16 ` Omar Polo
2021-10-11 17:17 ` Arthur Miller
2021-10-10 10:50 ` Andy Moreton
2021-10-10 11:21 ` Arthur Miller
2021-10-10 12:09 ` Stefan Kangas
2021-10-10 22:43 ` Campbell Barton
2021-10-11 1:34 ` Po Lu
2021-10-11 1:51 ` Campbell Barton
2021-10-11 3:04 ` Po Lu
2021-10-11 4:01 ` Campbell Barton [this message]
2021-10-11 8:20 ` Lars Ingebrigtsen
2021-10-11 13:00 ` Eli Zaretskii
2021-10-11 15:12 ` Stefan Monnier
2021-10-11 16:07 ` Eli Zaretskii
2021-10-11 21:14 ` Andy Moreton
2021-10-11 22:13 ` Ken Brown
2021-10-12 2:27 ` Eli Zaretskii
2021-10-12 10:39 ` Lars Ingebrigtsen
2021-10-12 14:09 ` Eli Zaretskii
2021-10-12 19:58 ` Paul Eggert
2021-10-13 2:24 ` Eli Zaretskii
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46728405-9441-4e3d-be5e-75e1bceaee70@gmail.com \
--to=ideasman42@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).