From: "Linda W." <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: linux scheduler and "cache-mate" processors
Date: Wed, 24 Jan 2007 16:10:15 -0800 [thread overview]
Message-ID: <45B7F567.7020100@tlinx.org> (raw)
I had a few questions about the linux scheduler and how it
interacts with in a 4 CPU system where the L2 cache is shared
between "pairs" (on same die) of processors.
Some of the later Core processors have 4MB of
L2cache/processor, and on a single chip, both processors have
access to the full 8MB of cache. At this point, AFAIK, Quad
processors are only implemented by putting 2 pairs of Core
chips and the two pairs don't share cache, acting, to some
extent, like a 2-socket system with Intel Dual Core
processors in each socket.
What I'm wondering is, say CPUs A&B share 1 cache, and C&D
share a 2nd cache.
1) does the scheduler know enough to try to spread tasks
equally over both the pairs to make best use of the 16MB total
cache? (i.e. given cpu bound processes "1" and "2", if they
are both on CPU "A", then the "C-D" cache remains unused, but
keeping "1" on "a" and "2" on "C" would tend to minimize
their caches being consumed by each other.
2) Since either A&B both have access to the 8MB cache, then
if a process was running on "A", it seems it would have a
low migration cost to be scheduled on "B" -- i.e. shouldn't
the process, if it were migrated to "A"'s "cache-mate", "B",
be able to benefit by any previous caching done on "A"?
If that's true, does the scheduler give preference, when
migrating a process, to a CPU's "cache-mate"?
If these things aren't in, are they planned for future or being
worked on?
Thanks,
Linda W.
next reply other threads:[~2007-01-25 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 0:10 Linda W. [this message]
2007-01-31 10:17 ` linux scheduler and "cache-mate" processors Arjan van de Ven
2007-01-31 20:20 ` Chuck Ebbert
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=45B7F567.7020100@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox