From: Tim Chen <tim.c.chen@linux.intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
David Rientjes <rientjes@google.com>,
Igor Mammedov <imammedo@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
brice.goglin@gmail.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] x86,sched: allow topologies where NUMA nodes share an LLC
Date: Wed, 4 Apr 2018 10:24:49 -0700 [thread overview]
Message-ID: <2d00edef-c8bf-2fc6-c342-274a0681e225@linux.intel.com> (raw)
In-Reply-To: <20180403211230.GA12842@alison-desk.jf.intel.com>
On 04/03/2018 02:12 PM, Alison Schofield wrote:
> +
> + /*
> + * topology_sane() considers LLCs that span NUMA nodes to be
> + * insane and will display a warning message. Bypass the call
> + * to topology_sane() for snc_cpu's to avoid that warning.
> + */
> +
> + if (!topology_same_node(c, o) && x86_match_cpu(snc_cpu)) {
> + /* Indicate that package has NUMA nodes inside: */
> + x86_has_numa_in_package = true;
Why does the x86_has_numa_in_package has to be set here when it would have
been done later in set_cpu_sibling_map?
> +
> + /*
> + * false means 'c' does not share the LLC of 'o'.
> + * Note: this decision gets reflected all the way
> + * out to userspace.
> + */
> +
> + return false;
Thanks.
Tim
next prev parent reply other threads:[~2018-04-04 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 21:12 [PATCH v4] x86,sched: allow topologies where NUMA nodes share an LLC Alison Schofield
2018-04-04 17:24 ` Tim Chen [this message]
2018-04-04 17:38 ` Alison Schofield
2018-04-04 18:42 ` Tim Chen
2018-04-04 19:00 ` Alison Schofield
2018-04-07 0:17 ` Alison Schofield
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=2d00edef-c8bf-2fc6-c342-274a0681e225@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox