NVIDIA Kepler speculation thread

Hate on charlie all you want, he's got better info than a lot of whats posted here usually and he's got info before anyone else usually, too. I watched him tell someone (senior in AMD) at AMD's Tahiti tech day what the next three generations codenames were, and the response 'Where do you get this info?!?!?!!'.

As for the 'backpedalling' you could say that, or you could say 'refining' as he gets better info digging into his stack of moles. He doesn't present it in a dry, passionless/emotionless manner but that's because he's not a peer-reviewed scientific paper.

I find it very interesting that GK110 is allegedly being brought forward to this year to fill in where GK100 won't be. AMD is 'making hay while the sun shines' with Tahiti.

Yeah only that now it seems Sea Islands really is AMD's next gen name and he was adamant that there is no Sea Islands and the next generation was Central Islands :)
 
Last edited by a moderator:
Hate on charlie all you want, he's got better info than a lot of whats posted here usually and he's got info before anyone else usually, too. I watched him tell someone (senior in AMD) at AMD's Tahiti tech day what the next three generations codenames were, and the response 'Where do you get this info?!?!?!!'.

As for the 'backpedalling' you could say that, or you could say 'refining' as he gets better info digging into his stack of moles. He doesn't present it in a dry, passionless/emotionless manner but that's because he's not a peer-reviewed scientific paper.

I find it very interesting that GK110 is allegedly being brought forward to this year to fill in where GK100 won't be. AMD is 'making hay while the sun shines' with Tahiti.

I think he's definitely "within", but I do not think it is appropriate to emphasize his articles: for example, only 3 months before the debut of the gtx 460, he claimed that the GPU would be simply "half GF100" ... http: / / semiaccurate.com/2010/04/05/new-nvidia-code-names-pop /
 
Lets not start digging out articles where Charlie was wrong or comparing them to the number where he was right and where it is debatable whether or not. He's running his website for hits and traffic, he has his sources and he has his way of interpreting things.
 
Lets not start digging out articles where Charlie was wrong or comparing them to the number where he was right and where it is debatable whether or not. He's running his website for hits and traffic, he has his sources and he has his way of interpreting things.

Oh i don't care too much about him, it's just to comment the news about kepler, easy :)
 
Yeah only that now it seems Sea Islands really is AMD's next gen name and he was adamant that there is no Sea Islands and the next generation was Central Islands :)

In English, 'C Islands' and 'Sea Islands' are phonetically the same, so over the phone you can see how they are confused; additionally, if you were looking to see who was ripping you off, you'd use that confusion to publish 'C.I.' as the next gen codename and see where it popped up. Charlie spends a lot of his time flushing out plagiarism. AMD have publicly called it 'Sea Islands' so that's the codename, until it's not. Like if it is actually 'C Islands' and it means 'Canary Islands' for example. But that's a group of Sea Islands, too. Round and round we go...


Fundamentally I believe Charlie above OBR. I base that on my entirely subjective personal opinion of having met and chatted with Charlie, vs. no idea who OBR is. /saltgrains

Is Charlie right about everything? No, and he doesn't make it easy for people to see what he's saying, either. Lots of snark, obfuscating real info to protect sources and see who's ripping him off; it makes general readability and information intake harder. Plus his articles are editorial, his opinion, speculation - not dry, just-the-facts-ma'am reporting. In some respects I find that more honest, as everybody editorializes, takes liberties, his is just way more obvious than others.
 
That's a little ambiguous in text.
There's :
"Egad! (monocle flies out) Where do you get this info?"
and
"Pshaw. Where do you get this info?"

If the former is how the AMD employee reacted, remind me to schedule a poker game with them.

There's a middle range of reactions; in this case it was an exasperated tone, but no extreme physical reaction; it was a convo over dinner, anyway.
 
No, and he doesn't make it easy for people to see what he's saying, either. Lots of snark, obfuscating real info to protect sources and see who's ripping him off; it makes general readability and information intake harder. Plus his articles are editorial, his opinion, speculation - not dry, just-the-facts-ma'am reporting. In some respects I find that more honest, as everybody editorializes, takes liberties, his is just way more obvious than others.

There's a thread dedicated to Charlie, if anybody really wants to paint him as hero, that's the place to do it. His relevance to a (hopefully) technical discussion about Kepler is unapparent to me, so I think that we should stick to that particular sort of discussing without dirtying it.
 
That's quite a quick update and just for the record's sake here are the first exclusive GK110 specifications:

4*32SPs/SM
8 TMUs/SM
4 SMs/GPC
8 GPCs
64 ROPs
850MHz

Where did you get that from...
256TMUs and 4096 SPs (even without hot clock) sounds too ambitious even for nvidia. Sounds more appropriate for a 20nm monster chip...
(I like the idea of more SPs per SM though which reduces the overdone geometry stuff a bit. I think that's what GK110 should about look like except I only really see that as possible on 28nm with 4 GPCs...)

psurge said:
Counts don't mean much if you don't know what each TMU/SP/ROP is capable of.
While that's true it seem a fair bet to assume a tmu has to be capable of single-cycle bilinear filtering (with all necessary adressing capabilities too of course) for at least int8, so there's imho not that much difference what makes sense as far as capabilites go for a tmu. Similar for SPs single cycle fma seems a given these days. ROPs probably are more diversified but then again that's the only number there which doesn't look outrageous :)
 
Last edited by a moderator:
There's a thread dedicated to Charlie, if anybody really wants to paint him as hero, that's the place to do it. His relevance to a (hopefully) technical discussion about Kepler is unapparent to me, so I think that we should stick to that particular sort of discussing without dirtying it.

Sorry, boss!

To topic; a tape out for GK110 now is almost a year behind AMD (tahiti/28nm); is that a large knock on effect from the interconnect problems - the fix implemented for GF110 caused abandoning GK100 to work on GK110 with improvements found in the fix stage of GF110?
 
caveman-jim said:
To topic; a tape out for GK110 now is almost a year behind AMD (tahiti/28nm); is that a large knock on effect from the interconnect problems - the fix implemented for GF110 caused abandoning GK100 to work on GK110 with improvements found in the fix stage of GF110?
What makes you think there are interconnect problems? It seemed to do its job just fine on Fermi.
 
Where did you get that from...
256TMUs and 4096 SPs (even without hot clock) sounds too ambitious even for nvidia. Sounds more appropriate for a 20nm monster chip...
(I like the idea of more SPs per SM though which reduces the overdone geometry stuff a bit. I think that's what GK110 should about look like except I only really see that as possible on 28nm with 4 GPCs...)

Isn't GK 110 rumored to be a dual GPU card? Specs make more sense that way.
 
Isn't GK 110 rumored to be a dual GPU card? Specs make more sense that way.
Don't think so. There wouldn't be enough rops with these specs for a dual card, unless these are some uber-rops (not that I think GF110 couldn't do with only 32 rops but reducing it (per chip) for next gen seems highly unlikely). At least unless you'd also assume that the dual card has more than 2x256bit memory interface. Unless that's really a chip only built for dual chip cards? Doesn't make much sense to me.
 
Sorry, boss!

To topic; a tape out for GK110 now is almost a year behind AMD (tahiti/28nm); is that a large knock on effect from the interconnect problems - the fix implemented for GF110 caused abandoning GK100 to work on GK110 with improvements found in the fix stage of GF110?

It does not have ot be the first tape-out. And he does not need to have the date correctly. Say the final production version tapped out late 2011 (late December), everything would be on target. Especially considering the limited 28nm wafers. (before Q3/12)
 
Back
Top