linux-kernel - linux scheduler and "cache-mate" processors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Jan 2007 16:10:15 -0800
From:	"Linda W." <lkml@...nx.org>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: linux scheduler and "cache-mate" processors

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/