From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Enable the option of more than 64 CPUs
Date: Wed, 04 Sep 2019 17:32:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14210@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
There is a new pull request by q5sys against master on the void-packages repository
https://github.com/q5sys/void-packages patch-1
https://github.com/void-linux/void-packages/pull/14210
Enable the option of more than 64 CPUs
With enterprise hardware now becoming cheaply available as well as the potential upcoming Threadripper 3 CPU (depending on what AMD does with it), it's getting very easy to surpass the current limit of 64 cpus on void. A HP DL580 G7 off ebay will run you $500-$1000 and can be configured with 40/80 (cores/threads). For those wanting even more power a HP DL980 G7 will run you ~$5k, and is 80/160.
Note: This does not require the MAXSMP flag to be enabled as SMP supports up to 512 CPUs. Also, this is only relevant to x86_64 CPUs, as other architectures supported by Void are not capable of hitting higher values than the default.
A patch file from https://github.com/void-linux/void-packages/pull/14210.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-14210.patch --]
[-- Type: text/x-diff, Size: 1411 bytes --]
From e068cad4003e49348ec9e1a983b4c6b08f88fa71 Mon Sep 17 00:00:00 2001
From: "q5sys (JT)" <jt@obs-sec.com>
Date: Wed, 4 Sep 2019 11:31:32 -0400
Subject: [PATCH] Enable the option of more than 64 CPUs
With enterprise hardware now becoming cheaply available as well as the potential upcoming Threadripper 3 CPU (depending on what AMD does with it), it's getting very easy to surpass the current limit of 64 cpus on void. A HP DL580 G7 off ebay will run you $500-$1000 and can be configured with 40/80 (cores/threads). For those wanting even more power a HP DL980 G7 will run you ~$5k, and is 80/160.
Note: This does not require the MAXSMP flag to be enabled as SMP supports up to 512 CPUs. Also, this is only relevant to x86_64 CPUs, as other architectures supported by Void are not capable of hitting higher values than the default.
---
srcpkgs/linux5.2/files/x86_64-dotconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/linux5.2/files/x86_64-dotconfig b/srcpkgs/linux5.2/files/x86_64-dotconfig
index b9609bb0ca9..a8eca2f5a15 100644
--- a/srcpkgs/linux5.2/files/x86_64-dotconfig
+++ b/srcpkgs/linux5.2/files/x86_64-dotconfig
@@ -355,7 +355,7 @@ CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_NR_CPUS_RANGE_BEGIN=2
CONFIG_NR_CPUS_RANGE_END=512
CONFIG_NR_CPUS_DEFAULT=64
-CONFIG_NR_CPUS=64
+CONFIG_NR_CPUS=256
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_SCHED_MC_PRIO=y
next reply other threads:[~2019-09-04 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:32 voidlinux-github [this message]
2019-09-04 15:35 ` voidlinux-github
2019-09-17 14:12 ` voidlinux-github
2019-09-17 14:20 ` voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14210@inbox.vuxu.org \
--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).