4 ms·
We've been having slices of L3$ tied to individual cores for a while now, so this is a bit more precedented than it sounds.
by Symmetry 5y ago
We've been having slices of L3$ tied to individual cores for a while now, so this is a bit more precedented than it sounds.
- evancox100 5y agoThis is quite a bit different. Yes, private cache is not new, whether that's L1, L2, or L3. But for multicore workloads, you HAVE to have some shared level(s) of cache for decent performance. Being able to have lots of fast/local per-core cache, and so have it do double duty as shared LLC is really new AFAIK.
- Symmetry 5y agoPreviously we had L2 caches that was only used by a particular core and slices of L3 which was tied to a particular core but could contain values used by other cores as well. Now we have L2 caches that are tied to a particular core but can contain values used by other cores as well. Especially with the partition into virtual L3 and virtual L4 I think this is an important evolution beyond your old MOESI or whatever but I'd still say that this is more evolutionary than revolutionary.