All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Borislav Petkov <bp@alien8.de>,
	"Charles (Chas) Williams" <ciwillia@brocade.com>,
	"M. Vefa Bicakci" <m.v.b@runbox.com>,
	Alok Kataria <akataria@vmware.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/smpboot: Make logical package management more robust
Date: Thu, 8 Dec 2016 14:04:34 +0100	[thread overview]
Message-ID: <20161208130434.GR3124@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1612081345450.3400@nanos>

On Thu, Dec 08, 2016 at 01:49:28PM +0100, Thomas Gleixner wrote:
> 
> > > -	if (logical_packages > __max_logical_packages) {
> > > -		pr_warn("Detected more packages (%u), then computed by BIOS data (%u).\n",
> > > -			logical_packages, __max_logical_packages);
> > > -		logical_packages_frozen = true;
> > > -		__max_logical_packages  = logical_packages;
> > 
> > So we'll never 'shrink' the initially computed max; which could result
> > in using more memory than strictly needed, otoh it makes physical
> > hotplug happier.
> 
> Yes. I was debating that back and forth and at the end decided that making
> it simple and robust is a good tradeoff vs. the slightly higher memory
> consumption. Though on most systems that's a non issue as number of
> possible cpus/packages is the same as the actual available ones. The insane
> setups have to suffer - rightfully so.

Don't we overestimate by a factor of 2 due to HT? That is, every single
socket Intel box will have a max_packages of 2.

Not that I care too deeply, and arguably the HT case _is_ insane because
its impossible to tell etc..

  reply	other threads:[~2016-12-08 13:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  9:04 [PATCH] x86/smpboot: Make logical package management more robust Thomas Gleixner
2016-12-08  9:13 ` Borislav Petkov
2016-12-08 11:03 ` Peter Zijlstra
2016-12-08 12:49   ` Thomas Gleixner
2016-12-08 13:04     ` Peter Zijlstra [this message]
2016-12-08 13:09       ` Thomas Gleixner
2016-12-09 22:06 ` Thomas Gleixner
2016-12-09 23:02   ` Boris Ostrovsky
2016-12-09 23:00     ` Thomas Gleixner
2016-12-10  3:37       ` Boris Ostrovsky
2016-12-10 19:03         ` Thomas Gleixner
2016-12-10 19:03         ` Thomas Gleixner
2016-12-10  3:37       ` Boris Ostrovsky
2016-12-10  3:27     ` Boris Ostrovsky
2016-12-10  3:27     ` Boris Ostrovsky
2016-12-10 19:09       ` Thomas Gleixner
2016-12-10 19:13         ` Thomas Gleixner
2016-12-10 19:13         ` Thomas Gleixner
2016-12-11  3:23           ` Boris Ostrovsky
2016-12-11  3:23           ` Boris Ostrovsky
2016-12-12 10:04             ` [PATCH v2] " Thomas Gleixner
2016-12-12 19:07               ` Boris Ostrovsky
2016-12-12 19:07               ` Boris Ostrovsky
2016-12-13 11:16               ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2016-12-13 11:16               ` tip-bot for Thomas Gleixner
2017-06-06 13:39               ` [PATCH v2] " Max Vozeler
2017-06-06 13:39               ` Max Vozeler
2017-06-07  1:48                 ` Boris Ostrovsky
2017-06-07  1:48                   ` Boris Ostrovsky
2017-06-07 12:19                   ` Max Vozeler
2017-06-07 12:19                     ` Max Vozeler
2016-12-12 10:04             ` Thomas Gleixner
2016-12-10 19:09       ` [PATCH] " Thomas Gleixner

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=20161208130434.GR3124@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akataria@vmware.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=ciwillia@brocade.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.v.b@runbox.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.