Intel Increases L1D and L2 Cache Sizes with "Ice Lake"

>Intel's next major CPU microarchitecture being designed for the 10 nm silicon fabrication process, codenamed "Ice Lake," could introduce the first major core redesign in over three years. Keen observers of Geekbench database submissions of dual-core "Ice Lake" processor engineering samples noticed something curious - Intel has increased its L1 and L2 cache sizes from previous generations.

>The L1 data cache has been enlarged to 48 KB from 32 KB of current-generation "Coffee Lake," and more interestingly, the L2 cache has been doubled in size to 512 KB, from 256 KB. The L1 instruction cache is still 32 KB in size, while the shared L3 cache for this dual-core chip is 4 MB. The "Ice Lake" chip in question is still a "mainstream" rendition of the microarchitecture, and not an enterprise version, which has had a "re-balanced" cache hierarchy since "Skylake-X," which combined large 1 MB L2 caches with relatively smaller shared L3 caches.

techpowerup.com/248825/intel-increases-l1d-and-l2-cache-sizes-with-ice-lake

@

THANK YOU, BASED BLUE!

Attached: intelicelake_chamada.jpg (640x360, 68K)

Other urls found in this thread:

archive.fo/G1nnG
crn.com/news/components-peripherals/300106631/intels-amd-talent-raid-raises-partner-buzz-around-gpu-blitz.htm
youtube.com/watch?v=V6T5j_HiwTQ
wired.com/story/tesla-self-driving-car-computer-chip-nvidia/
twitter.com/NSFWRedditGif

Incentivizing altcoin CPU mining on Cryptonight using L1/L2 cache?

“Being designed for 10nm” means it's still not here. Enlarging cache sizes is yet another stopgap.

>9900k is an overpriced housefire
>Ice Lake
Do they realize the irony?

They're supposed to have 3D die stacking by 2016 and that hasn't happened yet. If they could get that done, they could add even more cache.

While increased L1D$ and L2$ is very likely, Geekbench always reports them wrong.

Intel dropped 10 nm plans for now. Either they are going straight for 7 nm or re-trying after the restructure.
A lot of lay offs in any case and market will not react nicely.

In the end Intel has Jim Keller so I'm not worried.

Intel denied the rumour that 10nm was dead.

>slapping on some more cache memory
>major redesign...

Attached: 1519722969604.jpg (707x682, 74K)

Process technology is iterative, you don't just develop a working 7nm process when your 10nm is a massive failure, and it took you years to unfuck 14nm.
Their 10nm line is going to have relaxed pitches so they can actually start producing dies with marginal single digit yields. It won't have the area scaling they targeted, it won't have the power reduction they targeted, its likely that it'll never clock as well as 14++, but thats what they'll be delivering.

The situation with Keller isn't going to do them any good. He wasn't hired on to design core arch, he hasn't been moved there either. He isn't a process engineer or anything close to it. He can't fix their foundry business. He was hired for SoC integration; hes working on back end fabric, probably the successor to QPI. QPI was originally intel's equivalent to HyperTransport. They'll undoubtedly want more feature parity with AMD's Infinity Fabric for future chips so they don't fall miles behind in scaling potential.


Intel did PR damage control over the very real truth that their 10nm line as the originally presented it is 100% canceled. That isn't a rumor. They have a completely different process and they're calling it the same thing for PR sake.
The S|A article is nothing but factual archive.fo/G1nnG

>10 nm
Fake news.

Well yeah? Ofc they deny it.
They have postponed it numerous times by now, and in july finally they said 10 nm not until end of 2019.
It's pretty clear they are having fab issues.

Now we have a _major_ corporate restructure add to that, with the classic punch lines that nothing is happening or wrong.

I'm not saying they are abandoning 10 nm, but that they are canning the plan/roadmap and moving people around to start again.
Also see the Jim Keller snatch.

The writing is in the wall and now we are starting to hear confirmations from inside.

While I don't like Charlie, it's not like he hasn't got a perfect track record with shit like this.

Keller could have been snatched to gimp AMD, also he has a lot to give after AMD success.

It's a conflicting hire in any case and they must of have given him a serious package.

>Implying based Jim Keller isn't just in the second phase of his contract with AMD; sabotaging Intel from the inside and getting paid by both companies for it
Get ready for the 100-stage pipeline

Attached: Jim Keller at AMD.jpg (1680x1050, 425K)

>the first major core redesign in over three years
>L1 from 32kb to 48kb
>L2 from 256kb to 512kb

wow! it's fucking nothing. Intel feeding new info to the media to take some of the heat off the humiliating 9 series release

Snatched? Keller's employment contract was up with AMD. He wasn't brought on as a permanent hire, he was paid to work on only a couple projects, and left when they were finished. The high level core arch for Zen was finished and work on Zen2 had already begun before Keller departed. Its not like intel poached him while he was still working there.
Given his track record and how he moves around the globe I don't think hes the type of person content to ever settle down with one company.

They're writing about it because it has some small implication.
When it comes to caches larger ones almost always have lower latency. You don't ever want to increase latency unless you can justify it by having the average hit rate high enough, keeping more instructions there so they don't fall through the hierarchy or end up getting reissued which wastes cycles.
It might show that there are some other changes in the core arch which would produce higher IPC. Just adding cache doesn't solve anything unless it can actually justifiably be utilized.
Though that is a big stretch to write an article off of that one tidbit. Sites are all desperate for clicks. What can you do?

Well, I appreciate you taking the time to explain possible implications for IPC improvements or something.

Yet Smeltdown is still implemented kek.

#AMDnovulns

When do we hire Keller to do the ground work for a FOSS CPU?

When you have millions of dollars and a compelling sales pitch for recruitment.

So Keller is like a teddy bear with microphones in it that is passed around...

Low level techs have insane contracts that restrict working with competitors. Keller is a major and competent tech on the field. FFS he was brought to AMD to design Zen and had the title "CVP and Chief Architect for CPU Cores".

History books will show how Keller brought AMD from the swamp to compete and win Intel in Zen era.

Don't downplay this hire for Intel.

When he was rehired by AMD he oversaw the Zen and K12 design times. Dozens of lead designers each, an army of technicians behind them all. Because he was hired for that. Intel hired him to work on fabric, something else he has experience with. He was one of the people who developed the spec for HyperTransport.

I don't know why you're trying to make it seem like this is something more than it is. Intel didn't hire him to work on core arch.

>Intel didn't hire him to work on core arch.
I never said that. I implied that getting Keller was a good thing just for his knowledge of internal AMD state/matters.

Also it's not like Intel isn't on the headhunt for AMD techs, which was my other point.
crn.com/news/components-peripherals/300106631/intels-amd-talent-raid-raises-partner-buzz-around-gpu-blitz.htm

You just know they've run out of ideas when they double the cache.
It's a relatively straightforward way to boost performance but with thermal and die size tradeoffs, so it looks like Intel is in a deep shit with Ice Lake's performance - the arch hasn't moved forward and the 10nm process has lower performance so they're doing everything they can to make it at least as good as 14nm.
It's not without precedent either. they did the same thing to Itanium so it would appear to outperform their own Pentiums and Xeons.

POO IN THE JOO

Attached: 1535561310892.png (731x918, 65K)

>still can't fab anything bigger than a 2 core with dead GPU
Wew

Very fast. Whether the rumors are true or not, that tweet was pure damage control. They don't control the situation anymore and can't pull off "we don't comment on rumors" line because they aren't as mighty.

>Process technology is iterative.
Yes, to an extent, unless it's the introduction of a new design feature. Note that we're talking about front-end (transistor/below ML1) design features here, so this includes things like the gate stack (e.g., gate insulator, multiple and various diffusion and adhesion barriers, work function metals, fill metals), source/drain contact schemes (e.g., source/drain epitaxial (re)growth, heavy B/P doping methodologies, Ge content increases, silicidation), etc.

That said, both Intel and TSMC work in parallel on their upcoming nodes. Within a given company, there are separate groups working simultaneously on the more pressing 10 nm and 7 nm nodes (naming convention here is irrelevant, the two nodes most close at hand to high volume), and then another separate group working on the "what's next?" questions for 5 nm as well. If they're all well organized, information can be shared between groups (need to know basis) as well as the learning from the current production nodes. If they're not well organized and managed, you have what happened to Intel's 10 nm group.

>Relaxed pitches.
I mean, how often do you use minimum feature size for logic? The biggest impact that feature size scaling has on transistor density will always be with respect to cache, since (a) an SRAM cell is of a fixed, known design that will be uniformly repeated (barring any alterations to the fundamental design for LP operation, etc.), and (b) the amount of on-die real estate that cache takes up is huge.

>Power reduction.
I think this is the bigger factor here. Given that operating voltage scaling has gone out the window for some time now, the loss in power dissipation scaling and commensurate increase, however minor, in clock speeds would be a big blow.

>major core redesign
>still includes all the vulnerabilities
lmao so much for a redesign
>first major core redesign in over three years
Oh, so it's not really a redesign since the last microarchitecture change was like 10 years ago.

>Expecting the Jew to close the backdoors they left open for the NSA.
You really can't win these days.

>all these amdrones scared and shook as fuck when intel pays off tsmc's 7nm designs

>first major core redesign in over three years.
But Sandy Bridge came out 8 years ago.

>in over three years
But that would imply it getting released now, since Skylake was released three years ago. And even if 10 nm were here -- which it isn't -- they'd release the Cannon Lake refresh first. It's difficult to imagine Ice Lake being released prior to 2020 even in the best possible case.

>major core redesign
>major
Sure hope they're planning to do more than enlarge the caches to fit that bill.

>The L1 data cache has been enlarged to 48 KB
>The L1 instruction cache is still 32 KB in size
>the L2 cache has been doubled in size to 512 KB
Meanwhile, the A12 uses 128 kB L1D and L1I, and 8 MB L2, and get IPC accordingly.

Attached: ipc-1.png (816x275, 32K)

>BASED BLUE
Nothing they have done lately should be considered based.

>still includes all the vulnerabilities
But they were already fixed in CFL-R.

Intel can't plop their arch on TSMC 7nm and get the same performance w/o years of tuning.

Skylake-SP is a year old now, it has 1MB of L2 per core instead of 512.

and it is slower than mainstream cpu.

... No.

AMD Zen: 64KiB L1I, 32KiB L1D, 512KiB L2

fixed

Attached: i11.png (1280x720, 920K)

... yes.

Attached: ss.png (701x413, 52K)

>MAJOR core redesign
OH BOY THIS IS INTEL'S SEKRIT SAUCE BOYZ

MOAR CACHE

Increasing cache is not a fix-it-all solution to every CPU bottleneck.
A larger cache means higher access latency, which is something you absolutely want to avoid with low level caches. Also, power consumption.

COFFEE REFRESH COFFEE REFESH COFFEE REFRESH COFFEE REFESH COFFEE REFRESH COFFEE REFESH COFFEE REFRESH COFFEE REFESH

Attached: coffee.png (560x316, 348K)

That's oversimplified

Will Ocean Cove BTFO Zen?

Ok, let's make predictions.
14nm++++, 200W, barely any performance gain except a few specific apps, 1000$ for a 10 core, because have to compete with zen2.

>L2 cache has been doubled in size to 512 KB, from 256 KB
>2MB L3 per core

OK.

Attached: 2700x cpu-z.png (401x402, 24K)

Wait, actually, AMD beats the incoming intel in all cache metrics.

Well, a bigger instruction cache is basically a bigger bibeline.
I just hope we don't see the rise of Pentium4 2.0

When is Intel Lava Lake?

I-it's not fair bros! Isn't it mostly victim cache or something?

Attached: Taskmgr_2018-10-24_12-52-27.png (373x297, 8K)

Whoops.

Attached: cpuz_2018-10-24_12-54-52.png (403x402, 26K)

Bless AMD for giving you all the L3 even on a 6 core.

I thought that's what we're seeing right now?

On paper, it's great. But only on paper.

If I'm not mistaken, Keller paved the road up to Zen5.
Maybe he's just switching companies every five years, to milk them off.
But to be honest, I think even him thought 10nm was real.

*NEW* Cache doesn't matter!

Will the list ever stop growing?

*NEW* List entries don't matter!

>we AMD now
Next Intel will create new arch similar to AMD... OY VEY... I meant OH WAIT

Attached: 1540200373828.gif (359x346, 2.94M)

jim killer is working with raja koduri on GPU division

>jim "the pussy slayer" Keller: but intel you didn't hired me to make a complete new arch from scratch. Look, it says so in the this legal paper we both sign. Look!
>intel: ... then we make a new contract where we double your pay... triple if necessary...
>jim "the pussy slayer" Keller: Well now that you said triple my pay... My interest went up to "not so sure" mode :trollface:

It's that easy

Oh, I get it! It'll take an entire lake of ice just to cool the damn thing.

:^(

Attached: 1535727509926.png (767x326, 83K)

gonna need some more info on this pic
source for this?

> Ice Lake
> not Lava Lake

What's next? Seal coolers?

youtube.com/watch?v=V6T5j_HiwTQ

>slightly more cache
>IT'S A MAJOR REDESIGN!!!!
What the fuck?

JIDF at it again

Reminder that intel is floundering hard and with the management shake up they're going to be fucked even harder now

Ahh, wondered why there were so many anti-AMD threads today: Intel's on a marketing blitz.

>Multi-core doesn't matter!
>Productivity doesn't matter!
>Price/performance doesn't matter!
>Performance per watt doesn't matter!
>Power usage doesn't matter!
>Temperatures don't matter!
>Soldered dies don't matter!
>Stutters don't matter!
>Streaming doesn't matter!
>Data centers don't matter!
>Locked CPUs don't matter!
>OEMs don't matter!
>Hyperscalers don't matter!
>Upgradeability doesn't matter!
>Anti-competitive business practices don't matter!
>Locked platform features don't matter!
>Synthetic loads don't matter!
>PCI-e lanes don't matter!
>Burnt pins don't matter!
>Heat doesn't matter!
>1771w cooler doesn't matter!
>Server space doesn't matter!
>ECC support doesn't matter!
>Free RAID doesn't matter!
>NVMe RAID doesn't matter!
>StoreMI doesn't matter!
>IPC doesn't matter!
>7nm doesn't matter!
>StoreMI doesn't matter!
>HEDT doesn't matter!
>Stock coolers don't matter!
>Security doesn't matter!
>Games don't always matter!
>Enterprise doesn't matter!
>Hyperthreading doesn't matter!
>VMware doesn't matter!
>MySQL doesn't matter!
>Unix doesn't matter!
>Linux doesn't matter!
>Waffer yields don't matter!
>Benchmarks after full patches don't matter!
>Asian markets don't matter!
>Own fabrics don’t matter!
>Chipset lithography doesn't matter!
>Cray doesn't matter!
>Cisco doesn't matter!
>HPE doesn't matter!
>AZURE doesn't matter!
>*NEW* 5nm doesn't matter!
>*NEW* TDP doens't matter!
>*NEW* 10nm doesn't always matter!
>*NEW* Cache doesn't matter!

what this cache does

Its the other way around. He goes wherever he wants to work on whatever projects he wants. Incidentally, it just so happens to be that the companies that hire him have a need for those things he wants to work on, and have pretty much a blank check in the form of money and patience just for him.

Much of AMD's past success is because of Keller, after AMD he went to Apple. It's A10 is Keller's doing. A11 and A12 are both an iteration and then an evolution based on lessons learned by Apple's silicon engineers by working under and with Keller.

Then he went back to AMD and oversaw Zen. After that he left for Tesla, whose AI chip is expected to see a perf increase between 500 and 2000% compared to Nvidia's Drive PX/DGX platforms. Source: wired.com/story/tesla-self-driving-car-computer-chip-nvidia/

>2000 FP/s + redundancy which is a magnitude order better than Nvidia's offering (doing 200 FP/s + redundancy)

After he was done with Tesla, he went to Intel because he wanted to work on something and his and Intel's interests aligned. He's the kind of guy who can go ANYWHERE and say "I want to work on X" and the company in question will jump to the tune of X.

Keller doesn't give a shit about money, he wants to work on the technology because he's that fucking good. If he could work on the greatest piece of tech engineering for $150k, he'd do it, even if the company basically said "we'd pay you $500k instead". Of course, no one but him knows how much he makes--but he's the kind of guy, where money is not even on his dimension. It's a complete after thought for his passion of engineering.