From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Dave Hansen <dave@sr71.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
hpa@linux.intel.com, ak@linux.intel.com,
Alex Chiang <achiang@hp.com>, Borislav Petkov <bp@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Mike Travis <travis@sgi.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] x86: Consider multiple nodes in a single socket to be "sane"
Date: Tue, 16 Sep 2014 12:07:25 +0200 [thread overview]
Message-ID: <20140916100725.GB4796@osiris> (raw)
In-Reply-To: <5417F228.9060301@sr71.net>
On Tue, Sep 16, 2014 at 01:17:44AM -0700, Dave Hansen wrote:
> >> The sysfs effects here cause an issue with the hwloc tool where
> >> it gets confused and thinks there are more sockets than are
> >> physically present.
> >
> > Meh, so then we need another mask.
>
> s390 has this concept of a "book" although it's not obvious at all where
> this fits in to the hierarchy to me. The help text and comments are
> pretty funny:
>
> Book scheduler support improves the CPU scheduler's decision
> making when dealing with machines that have several books.
>
> Wow, really? Book scheduling helps with books? I would have never
> guessed.
I'm glad the help text did enlighten you.
> Wish I knew what a book was. :) Google helped a bit:
> http://sysmagazine.com/posts/150430/
> but it's still not clear. I think a book is below a node?
>
> SMT <= LLC <= MC <= BOOK <= NODE
This one is correct. s390 does not have NUMA support. So we have one
node with multiple books.
next prev parent reply other threads:[~2014-09-16 10:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 22:26 [PATCH] x86: Consider multiple nodes in a single socket to be "sane" Dave Hansen
2014-09-16 3:29 ` Peter Zijlstra
2014-09-16 6:38 ` Chuck Ebbert
2014-09-16 6:44 ` Ingo Molnar
2014-09-16 7:03 ` Chuck Ebbert
2014-09-16 7:05 ` Ingo Molnar
2014-09-16 16:01 ` Peter Zijlstra
2014-09-16 16:46 ` Dave Hansen
2014-09-16 15:59 ` Peter Zijlstra
2014-09-16 16:36 ` Dave Hansen
2014-09-16 8:17 ` Dave Hansen
2014-09-16 10:07 ` Heiko Carstens [this message]
2014-09-16 17:58 ` Peter Zijlstra
2014-09-16 23:49 ` Dave Hansen
2014-09-17 22:57 ` Peter Zijlstra
2014-09-18 0:33 ` Dave Hansen
2014-09-17 12:55 ` Borislav Petkov
2014-09-18 7:32 ` Borislav Petkov
2014-09-16 16:59 ` Brice Goglin
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=20140916100725.GB4796@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=achiang@hp.com \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dave@sr71.net \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.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 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.