From: Omar Polo <op@omarpolo.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Gnulib bugs <bug-gnulib@gnu.org>,
Stefan Kangas <stefan@marxist.se>,
Campbell Barton <ideasman42@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] support for accessing CPU/core count (processor-count)
Date: Sun, 10 Oct 2021 23:16:32 +0200 [thread overview]
Message-ID: <87pmscbmsb.fsf@omarpolo.com> (raw)
In-Reply-To: <9f927b85-c284-789a-36a7-041632156511@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 10/10/21 5:21 AM, Stefan Kangas wrote:
>> Omar Polo <op@omarpolo.com> writes:
>>> OpenBSD disables hyperthreading by default so HW_NCPU is (almost) always
>>> misleading. For example, on my machine
>>>
>>> % uname -a
>>> OpenBSD venera 7.0 GENERIC.MP#221 amd64
>>> % sysctl hw.ncpu
>>> hw.ncpu=8
>>> % sysctl hw.ncpuonline
>>> hw.ncpuonline=4
>>>
>>> and this has been the case for a while already (I mean, a couple of
>>> years if not more.)
>> BTW, Gnulib doesn't seem to make this distinction (lib/nproc.c:313).
>> Maybe that should be reported to the Gnulib developers?
>
>
> No need for a bug report as I'm one of those developers. To fix the
> Gnulib nproc OpenBSD issue I installed the first attached patch into
> Gnulib, and to port Emacs's recently-added processor-count code to
> more platforms I installed the second attached patch into Emacs's
> emacs-28 branch. Although I think the latter patch means that
> emacs/src/w32proc.c's w32-get-nproc function can be removed, I'll let
> the Emacs MS-Windows experts opine on that.
I had just cloned glib when I saw your mail :)
FWIW the first patch reads fine to me. Thanks!
next prev parent reply other threads:[~2021-10-10 21:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmscbmsb.fsf@omarpolo.com \
--to=op@omarpolo.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=ideasman42@gmail.com \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.