Don't know if it's actually part of the front-end or just happens to be right next to it, even the hi-res die shot doesn't really tell. But it should be clearly part of the core and Linley's core area is therefore inaccurate.
Don't know if it's actually part of the front-end or just happens to be right next to it, even the hi-res die shot doesn't really tell. But it should be clearly part of the core and Linley's core area is therefore inaccurate.The intriguing part I previously mentioned is that "New Caches" on the bottom right. If this is part of the front-end, I wonder if that could be some form of micro-op (or even trace) cache, but it would be oddly placed between L1I and L2. Or perhaps Apple went crazy and implemented a TAGE/ITTAGE larger than the I-cache
One of the sets of small boxes above the I-cache is most likely the tags.
Linley partitioning of Big/{Little,Small}/L2 (figure 3) is the same as yours, and I found no statement that the "New caches" structure has been excluded from the Big core area, so it should be right. Might have missed something...Don't know if it's actually part of the front-end or just happens to be right next to it, even the hi-res die shot doesn't really tell. But it should be clearly part of the core and Linley's core area is therefore inaccurate.
His core area estimate is missing the exact difference from that new cache block.Linley partitioning of Big/{Little,Small}/L2 (figure 3) is the same as yours, and I found no statement that the "New caches" structure has been excluded from the Big core area, so it should be right. Might have missed something...
One more addition.
I think the reason you and I so often butt heads is that for the most part I am asking "why" questions, and you (and people like you) are providing "what" answers.
For example, if you look at this latest dialog stream, MY concerns have to do with WHY one would structure a memory controller in a certain way as compared to various alternatives. Your answers, while giving various correct facts, do not answer that question. And this is the constant pattern I see between us.
It is reasonable for you to say that you do not know the answer to my "why" questions; it is NOT reasonable for you to insist that people are answering my questions and I am just being dogmatic in ignoring the answers. They are NOT answering the questions. They are providing various facts (sometimes relevant, sometimes of dubious relevance) but I am usually not asking for specific facts, I am asking, as I said, for a more abstract, conceptual theory of WHY these facts and not others.
Mark Liu CEO of TSMC stated that 10nm technology will be available to customers in late 2016 followed by expanded volume production in early 2017 which is when revenue from the first 10nm wafer sales are expected to roll in.
TSMC had faced serious challenges with its 16nm FinFET manufacturing process. The process faced three major setbacks amounting to nine months of delay.
After years of recruiting graphics architects, Apple has designed its own custom GPU, which is already shipping in the A8, A9, and A10 processors that power the iPhone 6, 6S, and 7. Based on publicly available evidence it is clear that the shader core in Apple’s GPU is architecturally very different from Imagination Technologies PowerVR line. This further implies that Apple wrote its own Metal and OpenGL ES compiler for its GPUs and almost certainly wrote the entire driver as well. The GPU in Apple’s processors still retains some fixed-function hardware from PowerVR, but the shader core and the driver are now developed internally.
With the case off, the phone lasted just under 30 minutes before stuttering again. So, yeah, I think it's throttling under the heat. At about 15 minutes, the phone was only moderately warm, but by about 25 minutes it was very warm. And a few minutes later is when it throttled.I think my phone is overheating.
I had a video file that was h.265 HEVC 1080p to play on my trip on the plane. My laptop is a Core 2 Duo and can't play that at all. Slideshow.
So, I put it on my iPhone 7 Plus instead. Playing the video, the phone in a plastic Spigen case over time got quite warm and then after about 20 minutes it started to get bad stuttering, which I interpreted as CPU throttling. If I stopped the video and then started playing it soon after, I'd get the same behaviour again in less than a minute. However, if I waited say 3 minutes, then I could play the video for several minutes before it started stuttering again. So it really does seem like throttling.
Mind you, with similar files before with an open back case, I didn't get that behaviour. Perhaps the files were a bit different, but I think the case used had a lot to do with it.
Overall though, 20 minutes of software based 1080p HEVC h.265 playback in an insulating case seems pretty decent. Maybe next time I'll try this same file with the case off to see what happens.
I do need a new laptop though. Can't wait for that Kaby Lake MacBook 12".
I think my phone is overheating.
I had a video file that was h.265 HEVC 1080p to play on my trip on the plane. My laptop is a Core 2 Duo and can't play that at all. Slideshow.
So, I put it on my iPhone 7 Plus instead. Playing the video, the phone in a plastic Spigen case over time got quite warm and then after about 20 minutes it started to get bad stuttering, which I interpreted as CPU throttling. If I stopped the video and then started playing it soon after, I'd get the same behaviour again in less than a minute. However, if I waited say 3 minutes, then I could play the video for several minutes before it started stuttering again. So it really does seem like throttling.
Mind you, with similar files before with an open back case, I didn't get that behaviour. Perhaps the files were a bit different, but I think the case used had a lot to do with it.
Overall though, 20 minutes of software based 1080p HEVC h.265 playback in an insulating case seems pretty decent. Maybe next time I'll try this same file with the case off to see what happens.
I do need a new laptop though. Can't wait for that Kaby Lake MacBook 12".
I once saw someone wondering why not everyone's on equal footing because they use the same equipment (IIRC). Intel's big push with Tick-Tock has always been their rapid node sucession within 2 years, with or without a full 2x shrink combined with their top notch rapid yield learning and Copy Exactly! With the yield learning having slowed down and 14nm not being a sole exception to the rule, it indeed seems the playing field in terms of density is leveling somewhat. But I don't see how anyone could achieve a major advantage .
Apple doesn't look like a nice place to work: pay is good but the paranoiac environment seems to be a pain. Intel is so big that unless you work in the Architecture Group or one of the design teams that work on Core/Xeon, you're too far from what is really interesting. Samsung might be an option, but the way Koreans work might be an obstacle to many.The world's attention has turned away from Intel, to mobile guys. The top mobile players are Apple and Samsung. If you are looking for work in an area related to chip design and manufacturing, would you want to go to a company with its future not being sure?
Those prejudices .Apple doesn't look like a nice place to work: pay is good but the paranoiac environment seems to be a pain.
Intel is so big that unless you work in the Architecture Group or one of the design teams that work on Core/Xeon, you're too far from what is really interesting.
Samsung might be an option, but the way Koreans work might be an obstacle to many.
In fact, there's a better company to work for if you're into chip design: ARM
Apple having LPDDR4-3200 is amazing! Intel used to be the first to implement latest RAM standards in the tech industry. Their laptops are still stuck to LPDDR3(because LP models offer advantage over non LP ones which is why they don't use DDR4), and high end desktops reach 3000 speeds only with enthusiast models. Now with A10 they have LPDDR4 with 4266 speeds. Fastest Skylake desktops barely reach that speed, and a puny mobile chip in a 5W envelope does that with an advanced PoP stack.