linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH] powerpc: update ibm,client-architecture
Date: Tue, 22 Dec 2009 11:58:41 +1100	[thread overview]
Message-ID: <20091222005841.GM30375@ozlabs.org> (raw)
In-Reply-To: <4B2FF35E.9020101@austin.ibm.com>

On Mon, Dec 21, 2009 at 04:14:54PM -0600, Joel Schopp wrote:

> It's a bad interface.  No matter what you choose there will be a
> downside.  1) If you choose NR_CPUS, the best case of how many you
> could boot without SMT, then when you boot with SMT2 or SMT4 you can
> get assigned more cpus than you can boot.  2) If you choose
> NR_CPUS/4, the worst case of how many you could boot, and you get a
> large machine with SMT2 or SMT1 you might have said you support less
> cpus than you actually do and thus not boot all the cpus.  So no
> matter what you choose you could be not booting cpus in some
> theoretical scenario.

We're far enough through boot to determine the threading model, so you /could/
work out what SMT we're in and divide NR_CPUS by that and give that to firmware.

Yours Tony

  parent reply	other threads:[~2009-12-22  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 21:07 [PATCH] powerpc: update ibm,client-architecture Joel Schopp
2009-12-20 23:59 ` Michael Neuling
2009-12-21 18:15   ` Joel Schopp
2009-12-21 21:12     ` Michael Neuling
2009-12-21 22:14       ` Joel Schopp
2009-12-22  0:33         ` Michael Neuling
2009-12-22  0:58         ` Tony Breeds [this message]
2009-12-21  0:44 ` Tony Breeds
2009-12-21 18:22   ` Joel Schopp
2009-12-22  0:18     ` Tony Breeds

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=20091222005841.GM30375@ozlabs.org \
    --to=tony@bakeyournoodle.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.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).