implementation will be a bit different for our dna but on not only the cpu stack with verizon and also milan they're showing milan x at the event but also um well cdnaNUMBER_TOKEN and obviously the fact of the matter is that NUMBER_TOKENd stacking and the capabilities of amd to do this essentially empower them to do a whole bunch of different crap and i've mentioned before that while it's very easy to say something like well the chip has like free chiplets i have said multiple times now that it's not really that easy you know it's not really all right really that simple at the end of the day it's the actual interconnectivity of these chiplets which are so important because not only are there well tons of technical issues like well making sure that each chip has enough memory bandwidth which is a fairly obvious one after all that's one of the jobs of in the infinity cache but you also need to make certain that when you have multiple uh chiplets especially when they're doing compute tasks that they're able to synchronize data and perform tasks in parallel so there's an awful lot of work here which quite frankly i think we just don't really know about so the NUMBER_TOKENd stacking approach does make sense and i kind of expect that we're going to be actually really blown away by what amd have done with their design i'm really looking forward to actually seeing an architectural breakdown of nave NUMBER_TOKEN and NUMBER_TOKEN as the NUMBER_TOKENd stacking text seems to be for NUMBER_TOKEN and NUMBER_TOKEN from what greyman has said and honestly it kind of matches up with what i've said a few times on channel as well i think it's going to be really cool with what we're going to be seeing in future tech for all of the different vendors but with that said thank you very much for checking out the video if you've enjoyed it well by golly gosh you know what to do you leave a likey on the video and of course subscribe to the channel and i'll see you soon take care of yourselves bye for now
NO_SEGMENT_TOKEN