Quantcast
[ 3 / biz / cgl / ck / diy / fa / g / ic / jp / lit / sci / tg / vr / vt ] [ index / top / reports / report a bug ] [ 4plebs / archived.moe / rbt ]

Due to resource constraints, /g/ and /tg/ will no longer be archived or available. Other archivers continue to archive these boards.Become a Patron!

/g/ - Technology


View post   

[ Toggle deleted replies ]
File: 437 KB, 500x510, isscc-2018-intel-10-sram-testchip.png [View same] [iqdb] [saucenao] [google] [report]
65935157 No.65935157 [Reply] [Original] [archived.moe] [rbt]

>2.2GHz Dual Core with a boost up to 3.1GHz
>no iGPU
>avx-512 (why the fuck i need avx-512 on a mobile cpu?)
>2 years late

http://tech-toniks.blogspot.com.br/2018/05/intels-10nm-finally-yields-chip.html

HAHAHA, INTEL IS FUCKING PATHETIC!

>> No.65935177 [DELETED] 
File: 614 KB, 992x1043, 1506383390040.png [View same] [iqdb] [saucenao] [google] [report]
65935177

>>65935157
THIS CAN'T BE HAPPENING

>> No.65935553

That's not bad at all at 4 watts.

>> No.65935636

>>65935553
Looks to me like they're attempting to make a low power server CPU. But that's just a guess.

>> No.65935663

>>65935157
took them 2 years to yield a single workable chip out of all the waffers?

>> No.65935665

>>65935553
It's 15W lmao

Heck, even at 4W it would be bad since no iGPU

>> No.65935714

>>65935665
At 4w it would be amazing. Supporting avx-512 is extremely expensive power-wise, granted 15w is more in line with what I'd expect from an engineering sample like this. I'm not bothered by the lack of iGPU, but it definitely means that they're gonna have to fight to show me what the use case is for this chip.

Honestly, this thing seems more like some sort of co-processor than a CPU. Shit's weird.

>> No.65935769

>>65935714
what kind of branch of 512 is supporting? if its full avx 512(doubtfull) there is no way in hell this is a 4watt
more like 40

>> No.65935770

I've never had so much Schadenfreude for a company before. It's truly pathetic how fucked Intel is for the foreseeable future

>> No.65935813

>>65935769
Agreed. I haven't seen any confirmed sources for power consumption. Just a bunch of brainlet anons shitposting.

I'm chalking this up to a waiting thread as per usual.

>> No.65935875

>>65935157
not news. we knew a year ago that intel cannot produce anything useful on their 10nm node, and this is confirmed by all those delays.
for the record, all intel igpus are on an earlier node than what the cpu is.
what does this mean? is intel incapable of mixing 10 and 14 nodes? sounds like it.

>> No.65935923

>>65935714
AVX512 uses nothing while its unused, that's why it has a 1000ms delay before it fully fires up on CPUs, making it worthless for bursty loads.
Also it's a U series CPU, meaning it's 15W

>> No.65936054

>>65935157
In the meanwhile AMD releases 7nm 2019, if were lucky even with 6 core CCX

>> No.65936373

>>65935875
what? all their integrated GPUs are fabbed on the same node as the CPU. You can't mix and match processes on the same die like that and they've never made a two die CPU+GPU processor.

>> No.65936402

>>65935813
15w TDP, no one has benched it yet
btw Kaby has a 2.2ghz bclk 3.4ghz boost with integrated GPU at 15w TDP; this Cannonlake is useless

>> No.65936404

>>65936373
>You can't mix and match processes
Clarkdale was CPU at 32nm and GPU at 45nm, though I'm unsure if that was a monolithic die

>> No.65936424

>>65935636
ARM is ded then

>> No.65936435

>>65935714
22x base upto 31x turbo for nonavx
max 8x for AVX loads.

>> No.65936440

>>65936404
oh thats the Northbridge transition processor where they put that on the same PCB as the CPU rather than the motherboard.

Wouldn't really count that as it also had the RAM controllers and a shitload of the IO stack

>> No.65936462
File: 152 KB, 502x600, Laughing_cars.jpg [View same] [iqdb] [saucenao] [google] [report]
65936462

>>65936435
>800mhz AVX2

>> No.65936475

>>65936462
>dorito cpu chip

>> No.65936950

>>65935714
Then why the fuck did they invent that shit called avx-512 if it's not optimizable? I really don't understand.

>> No.65937010

>>65935157
It's literally ivy bridge tier performance.

>> No.65937037

>>65936054
It's already confirmed to be 6 core CCX or more 4 core CCXs per Zeppelin die since there is a confirmed ebyn at 48 cores.

>> No.65937440

>>65937037
*fapfapfap*
7nm 12 core ~4.8 GHz

my dick almost explodes

>> No.65937499

what kind of temperatures can we expect from prime 95 small ffts with avx 512?

>> No.65937604

>>65936950
just a meme to sell h/w to idiots.
have you seen all those inteltards going nut about avx512?
they think that because 2 < 512, avx512 is better.

>> No.65937626

>>65935157
So this is why people call it "Intel's Bulldozer", huh? I didn't knew it was this bad, but man, they fucked up big time.

>> No.65937678
File: 348 KB, 350x233, 1e0.gif [View same] [iqdb] [saucenao] [google] [report]
65937678

>>65937440
>*fapfapfap*
back to plebbit you retarded, underaged fuck.

>> No.65937992

>>65935157
wew
no, this is far beyond pathetic, this is just sad. or extremely funny if you got no jewtel hardware or stocks and dont plan on getting any anytime soon

>> No.65938119
File: 614 KB, 992x1043, 1506383390040.png [View same] [iqdb] [saucenao] [google] [report]
65938119

>>65935157
THIS CAN'T BE HAPPENING

>> No.65938129

>>65935770
>Schadenfreude
>for a multi billion dollar multinational
>that is still seeing revenue gains every new quarter
I mean you can pretend you're better off than its CEO and all the major shareholders that are rolling in dosh but I doubt they really care about some neckbeard shitposting on 4chan.

>> No.65938164

>>65938129
No amount of money will save them from the heat death of the universe.

>> No.65938836

>>65935157
>no iGPU
>dual core
Nobody sane will buy this.

>>65935714
>not bothered by the lack of iGPU
So it's "power efficiency" is irrelevant then since you need a separate GPU.

>> No.65938851

>>65937678
>"back to plebbit"
>post Trump image
Pot, meet kettle.

>> No.65938874

>>65938851
Why do leftists try to pretend plebbit is right wing?

>> No.65939398

Reported for antisemitism

>> No.65939418

>>65938874
>>>/the_donald

>> No.65939608

>>65935714
You do realize it'd probably throttle to under 1GHz to run AVX-512 at the power, right?

Intel TDPs are fake. Especially fake when it comes to AVX.

>> No.65939624

>>65939608
800mhz got confirmed

>> No.65939638

>>65938874
You tell me, plebbitor.

>> No.65940009

>>65939624
O ok. I was just making an educated guess.

>> No.65940393

>l-look this w-we finally did t-the 10nm thing
It's just to keep shareholders happy. Worthless chip, more of a proof that they can actually do it if anything.

>> No.65940722
File: 23 KB, 200x200, 1504271097302.jpg [View same] [iqdb] [saucenao] [google] [report]
65940722

>>65935157
>2.2GHz
>no iGPU
>dual core
>15W

>> No.65940747

>>65937678
THE most reddit image in the history of reddit

>> No.65940908

does this chip have ANY advantages at all over their current kabylake/coffee lake mobile chips? other than avx 512 because that's just fucking retarded

>> No.65940961

AMD is going to destroy Intel over the next couple years. I really don't see them recovering. 10nm delays, high heat and non-soldering, expensive cooling and motherboards and no real progress. They don't even have a mainstream 8 core/16 thread CPU yet.

I think this is doom for Intel.

AMD will have 7nm Threadripper in the future, too. Think, a 16 core/ 32 thread CPU at 4.8Ghz.

Insanity. Intel is screwed.

>> No.65941049

Man, Intel is a bad meme at this point.
This is just fucking comical.

>> No.65941083

>>65940908
No. It only exists to say they got a 10nm chip out this year.

>> No.65941085

>>65940908
>Existing

>> No.65941089

They yields must be very bad if they're starting with mobile i3s

>> No.65941093

>>65935157
Well, hopefully they will make a better chip later.

>> No.65941107
File: 246 KB, 882x758, Intel1.png [View same] [iqdb] [saucenao] [google] [report]
65941107

>> No.65941142

>>65941089
Mobile i3s with no iGPUs

>> No.65941210
File: 130 KB, 274x385, 1483675906912.png [View same] [iqdb] [saucenao] [google] [report]
65941210

>>65935157
>Finally 10nm
>Mobile cpu instead
>Dont even have iGPU
>Muh power efficiency

>> No.65941248

>>65935157
HAHAHAHA

INTEL IS FINISHED

>> No.65941277

>>65940961
Intel will recover in 3-4 years once Keller is done with their new architecture

>tfw keller puts the CPU industry on his back

>> No.65941285

>>65935157
Yawn 7nm when

>> No.65941301

>>65938164
Intel will go the way of cyrix if they don't get Jim Keller to unwreck their shit

>> No.65941316
File: 990 KB, 1129x691, ScreenShot20180507at12.40.21PM.png [View same] [iqdb] [saucenao] [google] [report]
65941316

>>65938874
>>>r/the_donald

>> No.65941317

>>65941277
It would be real damn nice if he managed to double the IPC per core.

>> No.65941352

Zen 2 APUs are going to be amazing but AMD has to strong arm at least one major OEM into making a premium thinbook or w/e the AMD offbrand ultrabooks are called. AMD needs a Dell XPS in other words.

>> No.65941360

>>65941301
cyrix had a potentially shit-wrecking architecture very close to release before they were shutdown so even the shitwrecker himself might not save intel

>> No.65941873

>>65941277
Too bad Keller can't unfuck Intel's fabs

>> No.65941978

>>65936054
>if were lucky even with 6 core CCX
>>65937037
>It's already confirmed to be 6 core CCX or more 4 core CCXs per Zeppelin die since there is a confirmed ebyn at 48 cores.

the bad timeline alternative you're overlooking is 3*4c CCXs.
perhaps even more likely given rumors of 2nd gen 7nm 16c parts...

>> No.65942119

>>65935157

14 14+ 14++ 14FFL 14FFL+ 14FFL++?

14++ > 22FFL
22FFL+ ~ 14++

>> No.65942156

>>65939608
Intel's TDP specifies base clock on ark.intel does not include turbo boost so

>> No.65943661

>>65941277
Keller's working on SoC shit, I don't think he's doing anything involving a new architecture

>> No.65944002
File: 37 KB, 740x415, 448831-mix-and-match.jpg [View same] [iqdb] [saucenao] [google] [report]
65944002

>>65936373
This came out of one of the presentations they did last year. It does show both 10nm for the main cores and GPU though, but it also does show they are looking at mixing fab process on a single die as well.
So if they are having problems with the GPU they could potentially just stick with 14nm for it in the end.

>> No.65944032

>>65944002
That's not single die. Its an mcm using Intels emib designs, which are silicon Interconnects designed to be cheaper than a full interposer.

>> No.65944052

>>65941277
keller is good but even him cant do godly things to fix intel fabs

>> No.65944070

>>65936424
Other than learning a new machine language - with plenty of time before this tech is adopted - is that so bad?

>> No.65944403

>>65943661
Said the jews who also certainly don't have a nuclear program
>>65944052
Well, he now has the full might of Israel to back him though...

>> No.65944405

>>65944032
Cheaper, lower latency, faster

>> No.65944425

>>65944002
Kek, if intel wants to go that way with their marketing shilling, AMD should add to their dies a few 5mm transistors that do absolutely nothing and call their chips 5mm

>> No.65945229

>>65944403
Keller can't do shit to fix their 10nm process

>> No.65945437

>>65941978
So how would that work. Is thread brapper going from 16 cores to 24 by going to 3 of 6 packages instead of 2 out of 4?

>> No.65945512

>>65944403
keller is a cpu uarch engineer not a uvb god

>> No.65945638

>>65945437
no, still just:
- 2 die * 2 CCX/die * 6c/CCX, or
- 2 die * 3 CCX/die * 4c/CCX

>> No.65945700

>>65945638
>6c/CCX
can you even make 6 cores per CCX? i think it's more reasonable to make threadripper with more CCX per chip

>> No.65945738

>>65945700
it might be possible, but at the same time it would be offset by the fact adding 2 cores would vastly increase the complexity of the connections in the L3 cache, as every L3 slice must have a direct connection to every other L3 slice within the CCX, plus the connection to the nearest core.

My bigger question is what AMD is going to do to help mitigate memory bandwidth concerns, as 12C/24T blasting off 1 dual-channel DDR4 controller is going to cause issues. Mating some HBM to each die could help, but it would vastly increase the complexity of the packages and would make the resultant processors much more expensive because fucking no one can properly mass-produce 3-D stacked silicon yet without jacking the price up through the roof due to the less than stellar yields.

>> No.65945749
File: 134 KB, 954x605, 1492801783942.jpg [View same] [iqdb] [saucenao] [google] [report]
65945749

>>65945700
well, you either add more ports on the CCX/L3 internal crossbar, or you add more ports on the external Infinity Fabric one.

3*4c is clearly technologically easier, but 2*6c is doable and opens the door to quite a few other nice possibilities:
- 2c-6c laptops and APUs
- more model core count differentiation (4/6/8/10/12c workstation SKUs vs. just 6/9/12)

>> No.65945774
File: 17 KB, 594x364, edb71509528783.png [View same] [iqdb] [saucenao] [google] [report]
65945774

>>65945738
>My bigger question is what AMD is going to do to help mitigate memory bandwidth concerns, as 12C/24T blasting off 1 dual-channel DDR4 controller is going to cause issues.

Some rumor mills are spreading tales of 4 MB L3 per core. That, combined with 6c and 8c CCXs, would go a long way to help everything but purely streaming workloads.

>> No.65945795
File: 2.04 MB, 1056x999, 1525178689124.png [View same] [iqdb] [saucenao] [google] [report]
65945795

>>65941210
>dual core
>2018

>> No.65945822

>>65945774
That's alot of fucking L3 cache.

I suppose another option would be to fatten the IF bandwidth (either by doubling the IF clock or widening the pipes), then instead of pumping transistors into L3 caches, use them for an on-die L4 cache linked to the IF speed.

>> No.65945825

>>65945749
I don't think ddr4 fed graphics has much more in it currently. So my guess is the apu could easily be 8core with 12-16graphics cores. It would be far more marketable against Intels 8core with igpu. The graphics will still be bandwidth starved if there's no hbm and the 8core ccx can have reduced cache because it doesn't need to connect to other ccx or it's two 4core ccx while servers/desktop/hedt go 6core ccx.

>> No.65945846

>>65945774
This noname french magazine is intel shill. They post fake news from this account every time amd launches something. They posted fakes about 5GHz stock ryzen and then made fun of amd at launch as if they weren't the ones spreading fake news in the first place.
The funny thing is, their twitter had like literally 0 followers before jews started forcing it at ryzen launch.

>> No.65945850
File: 35 KB, 494x344, clarkdale_block.jpg [View same] [iqdb] [saucenao] [google] [report]
65945850

>>65936404
It indeed was not. Even some sandy bridge processors that don't use HD 2000 had a similar set up

>> No.65945876

>>65945822
>I suppose another option would be to fatten the IF bandwidth (either by
doubling the IF clock or widening the pipes)
this would crank power up dramatically and is only really likely to happen if AMD want to encourage DDR channel interleaving for higher single-consumer burst bandwidth.

> instead of pumping transistors into L3 caches, use them for an on-die L4 cache linked to the IF speed.
this will never, ever, happen.
one of the absolute best features of the Zen platform is the low local L3 latency.
IF is designed for max bandwidth per Watt at the cost of latency, so you absolutely don't want to be servicing half your L3 cache accesses over the data fabric.

>> No.65945924

>>65945876
>this will never, ever, happen.
>one of the absolute best features of the Zen platform is the low local L3 latency.
>IF is designed for max bandwidth per Watt at the cost of latency, so you absolutely don't want to be servicing half your L3 cache accesses over the data fabric.
Perhaps i should clarify a bit.

Instead of going with big fat L3s and the associated penalties those incur (if memory serves me correctly, the bigger a cache is the slower it is), The L4 cache i have proposed is to help with keeping the cores fed, as a hit to the on-board L4 cache would be significantly faster than running all the way out to main memory. It would essentially serve the same purpose as the eDRAM slab on the Broadwell chips equipped with it. It could also in theory free up some congestion on the IF network as instead of having to bounce all the way to the other CCX (or to a specific CCX on another die) for a chunk of data, it can send the request to the L4 slice.

>> No.65946020

>>65935157
>why the fuck i need avx-512 on a mobile cpu
I was gonna say "Why fucking bother with an i3 without a GPU", but clearly this is for server or embedded work.

>> No.65946022

>>65945924
for a cache to be meaningful it has to both have a substantial hit rate and a markedly lower latency than the next level of storage behind it.

I am saying the any sort of SRAM cache on the far side of the IF crossbar relative to a CCX is going to have not great latency even in a faster/wider fabric.
AMD has apparently deemed the typical % of data duplicated across CCX L3s low enough that the same amount of die space spent on local L3s helps more that that spent on a hypothetical UMC buffer etc.

>> No.65946034

>>65944002
Isn't the whole point that doing stuff on 10nm would be far more energy efficient than on 22nm? Cheaper, sure, but porting and fabbing shit down to 14nm shouldn't be too hard.

>> No.65946038

>>65936950
they keep updating simd instructions because the patents on older revisions eventually expire, which would allow other manufacturers to build x86 cpus and compete with them

>> No.65947301

>>65946034
If your stuff isn't working as it should at 10nm then it doesnt matter if it is more energy efficient or not. They are hitting the limit of the monolithic die and splitting things up will give far better yields.

>> No.65947337

>>65944002
You dunce, GPUs are way easier to fab than CPU cores. The only thing easier than a GPU is a memory controller.

>> No.65948522

>>65943661
>Keller's working on SoC shit, I don't think he's doing anything involving a new architecture
OH NO NONONONO AHAHAHHHAH

>> No.65949451

>>65945795
oy

>> No.65950418

>>65935157
Why the fuck would anyone want a dual core with a mobile dGPU?

>> No.65950457

>>65935157
>PLL
>BIST
>FUSE

>PLL
>BIT
>U

>PITBULL
Wtf this is DANGEROUS.

>> No.65950517

>>65937678
read his lips
he's not saying "you have to go back"
he's saying:
"You have to go Black"

>> No.65950535

>>65945850
>>65935157
does anyone actually understand these images (without the text ofc)?

>> No.65950560

>>65941277
I don't think Keller's interested in designing new architectures any more. AMD had him under contract and were desperate for a new one, yet Mike Clark designed Poozen, not Keller. He was tinkering with ARM-based horse shit that never came to anything.

>> No.65950632

>>65941142
maybe we're gonna see some netbooks with a 940m or some other old ass gpu

>> No.65950773

There better be good Zen2 APU laptops next year. The core lmao laptop is good for browsing and portable animu station, but I'd like to do actual work on it on the go.

>> No.65950840
File: 3.67 MB, 700x298, 1474403353062.gif [View same] [iqdb] [saucenao] [google] [report]
65950840

>>65950457
fucking kek

>> No.65950855

>>65950457
Lost.

>> No.65951084

>>65950560
Keller was chief architect and vice president of microprocessors. That was his official title and position at AMD. He was the boss of the entire CPU and soc arm of amd. He didn't touch any engineering except to set expectations, design philosophy, and tooling for all projects. He managed both projects and according to rumors a few years ago he was the one that killed the k12 project and didn't like the idea of arm servers to begin with despite the fact that k12 was more powerful than zen

>> No.65951137

>>65951084
Sorry, chief architect and vp of microprocessor cores. From the amd press release when he joined under Rory Read

http://m.marketwired.com/press-release/computer-architect-jim-keller-joins-amd-as-chief-of-processor-group-nyse-amd-1686018.htm

>> No.65951253

>>65951084
>le genius architect meme man
>actually shuffles papers while others do the work
No wonder he has to find a new company every few years.

>> No.65951311

>>65935157
>(why the fuck i need avx-512 on a mobile cpu?)
>why the fuck do we need optimized instructions on a mobile cpu?
Did you really make this thread?
I'm pretty sure this is just a thread to shit on AMD by making it seem like a AMD fanboy shitting on Intel.

>> No.65951328

>>65935553
Hello? We have M3 already that does better than that with a iGPU in terms of efficiency.

>> No.65951649
File: 1000 KB, 480x270, donkey.gif [View same] [iqdb] [saucenao] [google] [report]
65951649

>>65951311
>I'm pretty sure this is just a thread to shit on AMD by making it seem like a AMD fanboy shitting on Intel.
You're just a donkey

>> No.65951695
File: 21 KB, 183x183, 1525843642745.jpg [View same] [iqdb] [saucenao] [google] [report]
65951695

Does it still have the same heat issues as the previous ones? I'd rather just use the stock cooler but I'm considered about Meltdown.

>> No.65951706

>>65951695
*concerned

>>
Name (leave empty)
Comment (leave empty)
Name
E-mail
Subject
Comment
Password [?]Password used for file deletion.
Captcha
Action