all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Omar Polo <op@omarpolo.com>
Cc: Campbell Barton <ideasman42@gmail.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] support for accessing CPU/core count (processor-count)
Date: Sun, 10 Oct 2021 21:45:54 +0200	[thread overview]
Message-ID: <AM9PR09MB4977E059686764BFD8D4B68696B49@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <8735p8ensy.fsf@omarpolo.com> (Omar Polo's message of "Sun, 10 Oct 2021 20:17:49 +0200")

Omar Polo <op@omarpolo.com> writes:

> Arthur Miller <arthur.miller@live.com> writes:
>
>> [...]
>> And that is the beauty of having it as a Lisp function. You can just tweak it,
>> don't need to recompile entire Emacs :).
>
> I know I'm getting off-topic, but I just don't understand your point.  I
> don't see how spawning a bunch of commands, checking their return code
> and parsing their output is better than a couple of lines of C that do
> the right thing depending on the platform (decided at compile time!) and
> get directly an int.
I don't undestand what you don't udnerstand :-)

I don't know my man; what do you mean with "bunch of commands" and how you would
achieve this for all platforms with "couple of lines of C".

Here you have it; based on Andreas code from comp.el. I have just chagned part
shell command on gnu/linux since it can fail dependning on flags. Of course you
get an int back, "directly" :).

#+begin_src emacs-lisp
(declare-function w32-get-nproc "w32.c")

(defun processor-count ()
  (cond ((executable-find "nproc")
         (with-temp-buffer
           (call-process (executable-find "nproc") nil t nil)
           (string-to-number (buffer-string))))
        ((eq 'windows-nt system-type)
         (w32-get-nproc))
        ((eq 'berkeley-unix system-type)
         (string-to-number
          (shell-command-to-string "sysctl -n hw.ncpu")))
        (t 1)))
#+end_src

Compare to original patch in C, and tell me how is doing same in C better than
doing it in Lisp? Your Lisp routine should 
return an int directly. I don't see what is different there and what advantage C
will give you here; more than extra work to implement it and maintain it later on.

To note here is that 'shell-command-to-string' is not recommended since it can
return "more", than what expected, depending on what flags are used to pass to
bash. I am not sure if it can also differ if user uses some other
shell. call-process should be fine. I don't have a bsd system to test though.

I haven't used /proc/cpuinfo. It is a bit dependning on what is goal here: is it
to get number of "usable" cpus for spawning threads, or is it to get real
hardware number of cpus. The reason is that Emacs can run in a "restricted"
system such as a Docker environement where number of CPUs available can be
limited. /proc/cpuinfo (on linux kernel) records hardware number of cores but
nproc return "available" number. So you could have something like this:

#+begin_src emacs-lisp
(declare-function w32-get-nproc "w32.c")

(defun processor-hardware-count ()
  (cond ((eq 'gnu/linux system-type)
         (with-current-buffer (find-file-noselect "/proc/cpuinfo")
           (if (re-search-forward "cpu cores.*: " nil t)
               (string-to-number (current-word))
             1)))
        ((eq 'windows-nt system-type)
         (w32-get-nproc))
        ((eq 'berkeley-unix system-type)
         (string-to-number
          (shell-command-to-string "sysctl -n hw.ncpu")))
        (t 1)))
#+end_src

Could be done with "-all" flag to nproc too, but I think reading /proc/cpuinfo
is faster.

> I love lisp, don't get me wrong, and I actually prefer writing elisp
> rather than following the GNU C coding style (I love C too but GNU style
> hurts my eyes.)

Trust me; if anyone I always vote for doing it in C; but this one is probably
not worth doing in C. I have no idea how suggested posix sysconf deals with
restricted environements either.

> Sure, checking the number of cpus is not something that is done a lot,
> and I can't imagine a situation where it would be a bottleneck, but on
> the other hand, for the same argument, it's not something that needs to
> be tweaked often

Do you want hardware count; logical cores (think hyperthreading); should it work
in restricted environments? Quite a few things to take into consideration, isn't
it?

Hope you understand what I mean better after examples. Something tells me you
won't agree :-), but that is OK. I just present my opinion.




  reply	other threads:[~2021-10-10 19:45 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 [this message]
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
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=AM9PR09MB4977E059686764BFD8D4B68696B49@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=ideasman42@gmail.com \
    --cc=op@omarpolo.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 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.