From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Enable the option of more than 64 CPUs
Date: Tue, 17 Sep 2019 16:20:13 +0200 [thread overview]
Message-ID: <20190917142013.KspKEc43RCUHl814-C__kPjxX4-aXYNSk22OHmsfzt8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14210@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
New comment by q5sys on void-packages repository
https://github.com/void-linux/void-packages/pull/14210#issuecomment-532239314
Comment:
I'll redo my commit and submit a new PR.
The change could also be implemented for i686 processors, but as there are no i686 CPUs with this number of cores, it'd have no practical effect. I will do some digging and see if there is a specific override for multicore i686 systems somewhere else in the kernel config. I'm not aware of one from my puppylinux dev days, but I may have just forgotten. I'll check and make sure one way or the other.
I can't think of any i686 system with the possibility of more than 8 threads (old quad socket dual core Xeon systems). We can implement this in a i686 kernel for booting on x86_64 machines, but I'd be far more comfortable doing some testing on that before I send a PR for that. I'm not sure if there would be any complications for a large multiple core system running an i686 kernel. I'm pretty sure it wouldn't even boot on my machine due to the needed NUMA code that I'm guessing was never extended for i686 in the way it had been for x86_64. I have a bunch of older machines, so if your not opposed to it, i'd like to do testing of that before sending in a PR for the i686 kernel.
I don't want my first PR for your project to break the kernel.
next prev parent reply other threads:[~2019-09-17 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:32 [PR PATCH] " voidlinux-github
2019-09-04 15:35 ` voidlinux-github
2019-09-17 14:12 ` voidlinux-github
2019-09-17 14:20 ` voidlinux-github [this message]
2019-09-18 7:12 ` voidlinux-github
2019-09-21 15:25 ` voidlinux-github
2019-10-11 16:13 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-11 16:13 ` voidlinux-github
2019-10-11 16:15 ` voidlinux-github
2019-10-11 18:16 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190917142013.KspKEc43RCUHl814-C__kPjxX4-aXYNSk22OHmsfzt8@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).