6 ms·
Snapdragon 8 Gen 1's iGPU: Adreno Gets Big
- bigpaw 3y agoIs qualcomm capable of doing a flsgship cpu/gpu without overheating and high power usage?
- xlazom00 3y agoDoes anyone know if there is any processor(in phone) with SVE/SVE2? As SVE/SVE2 SHOULD be in all new ARMv9.0-A + CPU cores. I did have a chance to test only Qualcomm Snapdragon cores ( Samsung Galaxy S23).
- fotad 3y agoSnapdragon 888 probably the first one have SVE, Snapdragon 7/8 gen all have Qualcomm® Type-1 Hypervisor, so what's your test, abel to run any linux on it?
- xlazom00 3y agoI am using default android on Samsung Galaxy S23 with userland https://play.google.com/store/apps/details?id=tech.ula https://play.google.com/store/apps/details?id=tech.ula So any advice how to run it?
- monocasa 3y agoLooking at the docs, it doesn't look like ARMv9-A strictly requires FEAT_SVE to be implemented. What that means in practice is anyone's guess.
- my123 3y agoQualcomm disables SVE (masked at the hypervisor level) on all their silicon. If you want SVE on a phone roday, your options are Tensor G3, Exynos 2200/2400 or MediaTek phones with ARMv9 CPUs. Or if you have hypervisor execution level code exec (including an unfused phone), you can patch up that limitation.
- xlazom00 3y agoSo I have this https://en.wikipedia.org/wiki/Windows_Dev_Kit_2023 https://en.wikipedia.org/wiki/Windows_Dev_Kit_2023 And we can run ubuntu on that https://github.com/armbian/build https://github.com/armbian/build There isn't any hypervisor running on that and still no SVE So any advice ?
- my123 3y agoThis runs Cortex-X1C and A78C, which are of the generation _just_ before the one that got SVE
- rayiner 3y agoSnapdragon 800 -> Snapdragon 8 Gen N is terrible marketing. It makes everything sound like a point release.
- causi 3y agoMy headcanon is that Snapdragon 875 would've been a great chip unlike the infamously overheating 888.
- nfriedly 3y agoI'm on a Snapdragon 870 (moto g100), and it's great. Performance and battery life are both good enough that I don't think about it very often, and I've never had any overheating issues. I think the 870 was the highest end Snapdragon that didn't have any overheating issues for a while.
- joecool1029 3y ago5nm Samsung process was just bad. Needs active cooling. I've had the sm8250 (865 in my case) and it's a great chip that's faster in real-world conditions than the 888 hand warmer was. Now I have an 8 gen 2 device and it has no overheating issues. The 8 gen 1+ doesn't appear to have any either. I avoided the 8 gen 1 after having the bad experience with the 888.
- nfriedly 3y agoAah, ok, I edited my comment to just say that it was the best for a while, not still the best. Agree with you about Samsung's 5nm process.
- rbanffy 3y agoI believe their biggest failure in branding is to not put out Raspberry Pi-like small boards for people to experiment. Anyone with a slight interest in computers knows an M3 is a beast and that an i3 is meh. Almost nobody outside Qualcomm knows why a Gen 8 N is better than an 800 and what the difference would be.
- School-Cotton 3y agoThe title should say 8+, not 8 (@dang)
- nfriedly 3y agoYou're correct. But I believe they have an identical design - the only difference is that the 8+ runs a little faster and more efficiently, because it was manufactured by TSMC, whereas the 8 was manufactured by Samsung.
- clamchowder 3y agoThe 8+ runs at slightly faster clocks and has a smaller die. Somehow TSMC's 4 nm is better than Samsung's 4 nm. But yeah everything I wrote there should be applicable to the Snapdragon 8 Gen 1 as well, just without the 10% GPU clock speed increase that Qualcomm says the 8+ gets.
- cubefox 3y agoAny explanation why Qualcomm uses "tile based rendering" while Nvidia and AMD don't?
- charcircuit 3y agoBoth Nvidia and AMD do use tile based rendering
- kllrnohj 3y agoNot quite, not in the same way mobile GPUs do. Also I don't think AMD ever did the transition. They announced it (draw stream binning), but don't seem to have ever shipped it?
- bpye 3y agoAnd for what it’s worth Apple and Imagination do also - Imagination being where tiled rendering really started.
- kllrnohj 3y agoIt's significantly more bandwidth efficient to do tile based rendering however it has more performance cliffs and requires more game developer care to avoid hitting issues. For mobile SoCs (powervr, adreno, mali, and whatever apple calls their powervr-derivative) you can't just throw GDDR and get gobs of bandwidth, and also bandwidth is power expensive, so the savings more than offsets the performance cliffs and developer complications
- MikusR 3y agoNvidia has been using it for 10 years. https://www.realworldtech.com/tile-based-rasterization-nvidia-gpus/ https://www.realworldtech.com/tile-based-rasterization-nvidi...
- kbolino 3y agoIf you can afford to render the entire screen, why would you tile? Tiling complicates certain kinds of shaders, tiles have to be stitched together to make the final image, and tiling redraws (different parts of) the same triangles multiple times. On a dedicated GPU with lots of memory bandwidth, there's probably no benefit (and maybe even some penalty) to use tiling with lower resolutions (e.g. 1080p). However, 4K rendering might benefit from it and 8K rendering probably requires it.
- kllrnohj 3y agoFor the 'CPU to GPU Copy Bandwidth' section the more likely reason GPU -> CPU copy is slow is there's no reason to do it. Adreno is unified memory, you can just mmap that GPU buffer on the CPU. This is done on Android via the "gralloc" HAL, also called (A)HardwareBuffer. CPU->GPU is still valuable in that it's where texture swizzling happens to optimize the data for non-linear access, and vendors are all cagey about documenting these formats. But I don't think there's a copy engine for it at all, i think it's just CPU code. If you run a perfetto trace you can see adreno actually using multiple threads for this, likely why CPU->GPU is then so much faster than the reverse. But you almost never need non-linear output, so since vendor-specific swizzling isn't helpful you just don't bother and use shared memory between the two.
- flakiness 3y agoGreat article, as always! The author not only looks into the spec sheet and the presentation, but also looks into the OSS mesa code and uses OpenGL introspection to reverse-engineer (well, not by himself but...) the architecture. For me this is one of the most detailed explanations of how mobile GPU architecture looks like. The comparison to the older NVIDIA GPU is also very helpful (it is like a 6 year gap between this and discrete NVIDIA GPU 1050 GTX). Now I wonder how it compares to other mobile GPUs like Apple's or ARM's.