Skip to contentSkip to conversation

linux scheduler and "cache-mate" processors

DISCUSSION Linda W. 3 participants 3 messages Jan 25, 2007 – Jan 31, 2007

lore
Share & tools
lore

Linda W.

author
#0 lore 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.

#1 lore raw
Quoted 7 lines

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.

yes this works just fine

Quoted 7 lines

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"?

afaik yes as well

#2 lore raw
Quoted 21 lines · Arjan van de Ven
Quoted 7 lines

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.

yes this works just fine

Quoted 8 lines

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"?

Quoted 3 lines

afaik yes as well

You do have to enable "Multi-core scheduler support" in the kernel .config, though.