From: Andreas Schwab <schwab@linux-m68k.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: Omar Polo <op@omarpolo.com>,
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 19:27:03 +0200 [thread overview]
Message-ID: <877dekg594.fsf@igel.home> (raw)
In-Reply-To: <AM9PR09MB49772E1EDF4C2E813BB6F93396B49@AM9PR09MB4977.eurprd09.prod.outlook.com> (Arthur Miller's message of "Sun, 10 Oct 2021 18:35:11 +0200")
On Okt 10 2021, Arthur Miller wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> On Okt 10 2021, Arthur Miller wrote:
>>
>>> Does it differ between kernel versions or in which way is it architecture
>>> dependent on Linux kernel? I suggested this only for gnu/Linux.
>>
>> Every architecture is different. Why reinventing the wheel if the
>> standard library has already worked out all the details?
>>
> ? Which standard library? C? Or what?
>
> I think there is some missunderstanding going on here. I didn't oppose to the
> OPs idea with patch; I just said it would be more practical to implement it in
> Lisp than in C.
>
> I gave him /proc/cpuinfo for gnu/Linux
That is not portable. It is much easier to let sysconf do the heavy
lifting, instead of reimplementing it.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-10-10 17:27 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 [this message]
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=877dekg594.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=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.