#asahi-gpu · 2022-10-28 05:41
phiredepending on the exact impelementation, you might have to allocate some of the tile buffer for a copy of the depth buffer#asahi-gpu · 2022-10-28 05:40
phirealpha blending already puts the TBDR renderer into a very sub-optimal mode#asahi-gpu · 2022-10-28 05:39
phirethey already do#asahi-gpu · 2022-10-28 05:38
phirebecause alpha blending is somewhat expensive everywhere#asahi-gpu · 2022-10-28 05:38
phirelike more than 95% of your geometery in a typical game will be opaque#asahi-gpu · 2022-10-28 05:38
phirewhy not make it a bit more expensive?#asahi-gpu · 2022-10-28 05:37
phireyeah, and apple's docs go on and on about how alpha blending is expensive#asahi-gpu · 2022-10-28 05:37
phirewhich would have a side-effect that it has to fall back to single-cluster vertex processing when doing alpha blending#asahi-gpu · 2022-10-28 05:36
phireactually, maybe they cheat and their depth sorting implementation also sorts by primitive ID#asahi-gpu · 2022-10-28 05:34
phireand much larger diffrences if blending or image load/store are enabled#asahi-gpu · 2022-10-28 05:33
phirethere are very slight graphical diffrences (were depths are equal) if you render triangles out of API order#asahi-gpu · 2022-10-28 05:32
phireexcept you have to respect ordering, because stupid reasons#asahi-gpu · 2022-10-28 05:31
phireit's a lot less waseful when you put it that way#asahi-gpu · 2022-10-28 05:30
phireoh, point. we are just merging the indices#asahi-gpu · 2022-10-28 05:26
phireand reading and merging them in a single pass#asahi-gpu · 2022-10-28 05:25
phireHang on, is there any reason not to just implement reading from N TVBs (one per cluster) duing the 3d invocation?#asahi-gpu · 2022-10-28 05:22
phirebut merging also has better scaling?#asahi-gpu · 2022-10-28 05:22
phirebut merging just seems wasteful#asahi-gpu · 2022-10-28 05:22
phireyes, there would be scaling issues#asahi-gpu · 2022-10-28 05:21
phireor N centralied blocks, addressed by screenspace location#asahi-gpu · 2022-10-28 05:21
phireeach compute core sets final vertex data to a centralized block, which sorts it and writes it to the TVB#asahi-gpu · 2022-10-28 05:21
phirethe other option is a centralized vertex-writeback block, basically equlivant to the ROPs for pixels on desktop gpus #asahi-gpu · 2022-10-28 05:19
phireI guess it does need to be sorted into API order, which would be hard without a pass over it#asahi-gpu · 2022-10-28 05:19
phireso you can actually see it merging?#asahi-gpu · 2022-10-28 05:16
phireI wonder if it just aborts any tile that doesn't finish quick enough#asahi-gpu · 2022-10-28 05:12
phireI'm not sure what their expected preemption granularity is. it would be weird for a single tile to exeute for longer than ~10us #asahi-gpu · 2022-10-28 05:10
phirebut I would think indivudal tile infocations could be long enough that it's worth preempting them#asahi-gpu · 2022-10-28 05:08
phirebut vertex/fragment jobs are useally short enough that you can just wait for them to end#asahi-gpu · 2022-10-28 05:08
phiresome of those compute jobs are long-running. I wonder if compute launches require buffers for compute unit state#asahi-gpu · 2022-10-28 05:07
phirethe framebuffer#asahi-gpu · 2022-10-28 05:06
phirethere is already memory allocated for tiles, though we don't know if it's used#asahi-gpu · 2022-10-28 05:06
phireyes, was just going to say#asahi-gpu · 2022-10-28 04:59
phiremakes sense#asahi-gpu · 2022-10-28 04:55
phire(that's not something I've learned to spot on a die shot)#asahi-gpu · 2022-10-28 04:54
phirehow can you tell they are PLLs?#asahi-gpu · 2022-10-28 04:54
phire(at the bottom)#asahi-gpu · 2022-10-28 04:53
phireyeah, you might be right that it's just something sitting in otherwise unused space#asahi-gpu · 2022-10-28 04:53
phireso I'm thinking tags?#asahi-gpu · 2022-10-28 04:52
phirein a way that reminds me of zen 2's l3 cache. but it doesn't look like a cache#asahi-gpu · 2022-10-28 04:52
phireI mean, it's made of 2-4 symetric slices. but those slices seem to be tied together into a single block#asahi-gpu · 2022-10-28 04:49
phirethoery: top is inter-cluster dispatch; middle one is inter-cluster coherency fabric; bottom is for inter-die coherrency/comunication#asahi-gpu · 2022-10-28 04:47
phirethe bottom one might be to do with inter-die work sharing#asahi-gpu · 2022-10-28 04:46
phirethat might actually be three common areas. One at the top, one in the middle, one at the bottom. top and bottom seem to be diffrent#asahi-gpu · 2022-10-28 04:45
phireor draw VBO if that's enabled. not sure which path is used by default#asahi-gpu · 2022-10-28 04:44
phireyeah, the mesh is just a single DrawArrays call#asahi-gpu · 2022-10-28 04:41
phireinteresting, so it's splitting vertex workloads at a pretty fine granularity. Within a single draw?#asahi-gpu · 2022-10-28 04:39
phireif the guranuality is that small, I wonder if it can split vertex workloads across clusters. Or if vertex workloads are limited to a single cluster#asahi-gpu · 2022-10-28 04:37
phirescrolls down to correct die shot#asahi-gpu · 2022-10-28 04:37
phireso it's 4 cores per cluster? #asahi-gpu · 2022-10-28 04:35
phireyeah, I was supicious about the actual "gpu count" based on some of the initdata