From: Dave Hansen <dave.hansen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Alison Schofield <alison.schofield@intel.com>,
Ingo Molnar <mingo@kernel.org>, Tony Luck <tony.luck@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
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 v3] x86,sched: allow topologies where NUMA nodes share an LLC
Date: Thu, 29 Mar 2018 07:34:58 -0700 [thread overview]
Message-ID: <8a24d82e-a8dd-2f35-4764-a58fd6c64ae8@linux.intel.com> (raw)
In-Reply-To: <20180329134723.GA4043@hirez.programming.kicks-ass.net>
On 03/29/2018 06:47 AM, Peter Zijlstra wrote:
> The issue is that HPC workloads care about cache-size-per-cpu measure,
> and the way they go about obtaining that is reading the cache-size and
> dividing it by the h-weight of the cache-mask.
That works, but only if the memory being accessed is slice/node-local.
If it's spread across the package, it'll be wrong.
But, the HPC folks are the ones that are the most likely to have good
NUMA affinity, so that would seem to point us in the direction of both
halving the size and the mask so that the LLC _looks_ split to userspace.
> Now the patch does in fact change the cache-mask as exposed to
> userspace, it however does _NOT_ change the cache-size. This means that
> anybody using the values from sysfs to compute size/weight, now gets
> double the value they ought to get.
>
> So either is must not change the llc-mask, or also change the llc-size.
IOW, don't make it look like we've either doubled or halved the exposed
size of the llc.
> Which then leads to the conclusion that the current:
>
>> + /* Do not use LLC for scheduler decisions: */
>> + return false;
>
> is wrong. Also, that comment is *completely* wrong, since the return
> value has *nothing* to do with scheduler decisions
OK, got it. That comment betrayed my ignorance. I'm glad we put it there.
What should we say, though?
/*
* false means 'c' does not share the LLC of 'o'.
* Note: this decision gets reflected all the way
* out to userspace
*/
return false;
next prev parent reply other threads:[~2018-03-29 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 0:00 [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC Alison Schofield
2018-03-29 13:16 ` Thomas Gleixner
2018-03-29 13:45 ` Dave Hansen
2018-03-29 13:57 ` Peter Zijlstra
2018-03-29 13:47 ` Peter Zijlstra
2018-03-29 14:34 ` Dave Hansen [this message]
2018-03-29 16:09 ` Peter Zijlstra
2018-03-29 16:25 ` Dave Hansen
2018-03-29 16:29 ` Luck, Tony
2018-03-29 14:37 ` Dave Hansen
2018-03-29 14:55 ` Peter Zijlstra
2018-03-30 3:20 ` kbuild test robot
2018-03-30 17:34 ` 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=8a24d82e-a8dd-2f35-4764-a58fd6c64ae8@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.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=tim.c.chen@linux.intel.com \
--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