From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: Setup a scheduling domain for highest level cache.
Date: Mon, 24 Oct 2016 18:04:59 +0000 [thread overview]
Message-ID: <20161024.140459.1263760552719699072.davem@davemloft.net> (raw)
In-Reply-To: <1476923609-11125-1-git-send-email-atish.patra@oracle.com>
From: Atish Patra <atish.patra@oracle.com>
Date: Wed, 19 Oct 2016 18:33:29 -0600
> Individual scheduler domain should consist different hierarchy
> consisting of cores sharing similar property. Currently, no
> scheduler domain is defined separately for the cores that shares
> the last level cache. As a result, the scheduler fails to take
> advantage of cache locality while migrating tasks during load
> balancing.
>
> Here are the cpu masks currently present for sparc that are/can
> be used in scheduler domain construction.
> cpu_core_map : set based on the cores that shares l1 cache.
> core_core_sib_map : is set based on the socket id.
> The prior SPARC notion of socket was defined as highest level of
> shared cache. However, the MD record on T7 platforms now describes
> the CPUs that share the physical socket and this is no longer tied
> to shared cache.
>
> That's why a separate cpu mask needs to be created that truly
> represent highest level of shared cache for all platforms.
>
> Signed-off-by: Atish Patra <atish.patra@oracle.com>
> Reviewed-by: Chris Hyser <chris.hyser@oracle.com>
Applied, thank you.
prev parent reply other threads:[~2016-10-24 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 0:33 [PATCH] sparc64: Setup a scheduling domain for highest level cache Atish Patra
2016-10-24 18:04 ` David Miller [this message]
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=20161024.140459.1263760552719699072.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.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.