11–20 of 179 posts
Can someone explain if the 3D Vcache are stacked on top of each other or side by side. If they are stacked then why not 9800X3D2?
The 99xx chips have two CPU dies, and one cache die is on each CPU die.
Crazy to think that my first personal computer's entire storage (was 160MB IIRC?) could fit into the L3 of a single consumer CPU! It's probably not possible architecturally, but it would be amusing to see an entire early 90's OS running entirely in the CPU's cache.
Crazy to think that my first personal computer's entire storage (was 160MB IIRC?) could fit into the L3 of a single consumer CPU! It's probably not possible architecturally, but it would be amusing to see an entire early 90's OS running entirely in the CPU's cache.
Crazy to think that my first personal computer's entire storage (was 160MB IIRC?) could fit into the L3 of a single consumer CPU! It's probably not possible architecturally, but it would be amusing to see an entire early 90's OS running entirely in the CPU's cache.
KolibriOS would fit in there, even with the data in memory. You cannot load it into the cache directly, but when the cache capacity is larger than all the data you read there should be no cache eviction and the OS and all data should end up in the cache more or less entirely. In other words it should be really, really fast, which KolibriOS already is to begin with.
Crazy to think that my first personal computer's entire storage (was 160MB IIRC?) could fit into the L3 of a single consumer CPU! It's probably not possible architecturally, but it would be amusing to see an entire early 90's OS running entirely in the CPU's cache.
I wonder how much faster dos would boot, especially with floppy seek times...
If you run a VM on a CPU like this, using a baremetal hypervisor, you can get very close to "everything in cache".
Earlier quoted context omitted.
KolibriOS would fit in there, even with the data in memory. You cannot load it into the cache directly, but when the cache capacity is larger than all the data you read there should be no cache eviction and the OS and all data should end up in the cache more or less entirely. In other words it should be really, really fast, which KolibriOS already is to begin with.
Unless you lay everything out continuously in memory, you’ll still get cache eviction due to associativty and depending on the eviction strategy of the CPU. But certainly DOS or even early Windows 95 could conceivably just run out of the cache
For comparison, 9950X3D have a total cache of 144MB.
Earlier quoted context omitted.
KolibriOS would fit in there, even with the data in memory. You cannot load it into the cache directly, but when the cache capacity is larger than all the data you read there should be no cache eviction and the OS and all data should end up in the cache more or less entirely. In other words it should be really, really fast, which KolibriOS already is to begin with.
Unless you lay everything out continuously in memory, you’ll still get cache eviction due to associativty and depending on the eviction strategy of the CPU. But certainly DOS or even early Windows 95 could conceivably just run out of the cache
Edit: Also this 192MB of L3 is spread across two Zen CCDs, so it's not as simple as "throw it all in L3" either, because any given core would only have access to half of that.
Crazy to think that my first personal computer's entire storage (was 160MB IIRC?) could fit into the L3 of a single consumer CPU! It's probably not possible architecturally, but it would be amusing to see an entire early 90's OS running entirely in the CPU's cache.
In my case it began with 16K (yes, 16 1024 bytes) and 90K (yes, 90 1024 bytes) 5.25" floppy disks (although the floppies were a few months after the computer). Eventually upgraded to 48K RAM and 180K double density floppy disks. The computer: Atari 800.
Can someone explain if the 3D Vcache are stacked on top of each other or side by side. If they are stacked then why not 9800X3D2?