From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Enable the option of more than 64 CPUs
Date: Fri, 11 Oct 2019 20:16:58 +0200 [thread overview]
Message-ID: <20191011181658.x7bPD4nwPh9l4VbYGIJPB3bHpxF6Kw35AtL_RqlpTt4@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: 807 bytes --]
There's a merged pull request on the void-packages repository
Enable the option of more than 64 CPUs
https://github.com/void-linux/void-packages/pull/14210
Description:
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.
prev parent reply other threads:[~2019-10-11 18:16 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
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 ` voidlinux-github [this message]
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=20191011181658.x7bPD4nwPh9l4VbYGIJPB3bHpxF6Kw35AtL_RqlpTt4@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).