3 ms·
My comment on the register file is this: instead of making it 6r3w (6 read 3 write), just make it 2r3w and plop down 3 copies of it - each copy has 2 read ports
by phkahler 9y ago
My comment on the register file is this: instead of making it 6r3w (6 read 3 write), just make it 2r3w and plop down 3 copies of it - each copy has 2 read ports feeding a local ALU and writes go to all instances. Then to add another ALU you make a 2r4w register file and plop down 4 instances of it - one connected to the new ALU. This is still only 6 ports total compared to 9 on the one they've got. Routing within the file should be much easier. The tradeoff is multiple instances of it.
- sitkack 9y agoArea is the new clock speed.
- StringyBob 9y agoAlthough not obvious to consumers, area has always been the bottom line - Gordon Moore used to call the biz 'expensive real estate' (about $1bn/acre)
- ajross 9y agoOh sure. But the text as I read it seemed to imply that the issue was the library they were using had hugely wasteful flip flops or something, or was unable to route above them, or something crazy. It seems (and I'm not expert or professional in this space) that everyone who's used these EDA tools has experiences like this, and hates them. Seems like a great target for innovation at a lower margin, especially now that ASIC development is becoming commoditized.
- _chris_ 9y agoHi phkahler, the ultimate critical path is the load data coming back to the register file. Replicating the register file doesn't end up being a win (there would be so much area to broadcast it out to), otherwise, everybody would do it.
- phkahler 9y agoHi Chris! But it must alleviate the routing problem within the register file no? And the scalability would be better right? I mean, you can't possibly expect to add another ALU to Boom and require 4 write & 8 read ports can you? Does AMD use 12r6w It seems there has to be a better way ;-)
- jabl 9y agoSplit up the physical register file so each pipe has it's own fraction of it, and have the register renaming logic "route" to the correct fraction? Well, that's what BOOMv2 partially does by splitting the INT and FP register files, so I guess I'm proposing splitting the INT file further [1]? [1] This has probably been thought of and dismissed a million times over by actual experts. Say, losing whatever advantages it may have due to extra micro-ops needed to move stuff back and forth to the correct register file fraction?
- _chris_ 9y ago> Split up the physical register file so each pipe has it's own fraction of it, and have the register renaming logic "route" to the correct fraction? Have I got the paper for you! From my adviser's previous student: https://dspace.mit.edu/handle/1721.1/34012 https://dspace.mit.edu/handle/1721.1/34012 But you're right -- the win isn't obvious. There's pain and advantages in both directions. I've always wanted to build it, but I only have so much time in the day. :(