3 ms·
Random read and write of a big memory region could now presumably cause double the number of DRAM accesses, and half the performance, since the tag mapping will
by londons_explore 6y ago
Random read and write of a big memory region could now presumably cause double the number of DRAM accesses, and half the performance, since the tag mapping will need to be read in addition to the actual data. If the read of a memory address could have side effects (as is common with memory mapped hardware), does the hardware give guarantees that the tag will be checked before the memory is read or written? If so, that'll be an even bigger performance hit...
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- bitwize 6y agoIt seems that the tag mappings will need to live in separate physical RAM, so that info could be pulled from the tagmap RAM chips at the same time as the data is pulled from the data RAM chips. Using multiple RAM chips to increase throughput is an old computer engineering technique; it was, for instance, the entire justification for planar graphics modes in early graphics hardware.
- Retr0spectrum 6y agoYou're overlooking a) existing page table lookup overhead b) hierarchical caching.