From: Peter Zijlstra <peterz@infradead.org>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: nr_cpu_ids vs AMD 3970x(32 physical CPUs)
Date: Fri, 3 Jul 2020 19:45:39 +0200 [thread overview]
Message-ID: <20200703174539.GA4800@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAEJqkgiFFh8CvXkM4ZzXxNQmOJLL7WcgDL6rM83safNgEewZ9w@mail.gmail.com>
On Fri, Jul 03, 2020 at 07:07:39PM +0200, Gabriel C wrote:
> I boot all the boxes restricting the cores to the correct count on the
> command line.
This, because you're right about the wasted memory.
> Wasted resource or not, this is still a bug IMO.
Yeah, but not one we can do much about I think. It is the BIOS saying it
wants more because it expects someone to come along and stick another
CPU in.
Possible we could say that for single socket machines overprovisioning
is 'silly', but then, I've no idea how to detect that. You'll need to
find an ACPI person.
next prev parent reply other threads:[~2020-07-03 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 15:57 nr_cpu_ids vs AMD 3970x(32 physical CPUs) Uladzislau Rezki
2020-07-03 16:56 ` Peter Zijlstra
2020-07-03 17:09 ` Uladzislau Rezki
2020-07-03 17:38 ` Peter Zijlstra
2020-07-03 19:26 ` Uladzislau Rezki
2020-07-03 17:07 ` Gabriel C
2020-07-03 17:24 ` Uladzislau Rezki
2020-07-03 17:45 ` Peter Zijlstra [this message]
2020-07-03 18:36 ` Gabriel C
2020-07-03 19:05 ` peter enderborg
2020-07-03 19:28 ` Uladzislau Rezki
2020-07-03 20:08 ` Linus Torvalds
2020-07-03 21:20 ` Uladzislau Rezki
2020-07-03 21:51 ` Matthew Wilcox
2020-07-03 22:22 ` Uladzislau Rezki
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=20200703174539.GA4800@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nix.or.die@googlemail.com \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.org \
--cc=urezki@gmail.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.
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).