Ehh... unless you have more specific knowledge that’s still under NDA, the reasonable assumption is that the CPU still mmap()es the file into the GPU’s address space, and then the CPU pages in data from the SSD as the GPU generates page misses. Which is technically possible on PCs today, but isn’t done because you can’t assume fast SSDs and you definitely can’t assume shared memory. (actually I’m pretty sure discrete GPUs can generate page misses for mapped CPU memory, but I’m not certain which graphics APIs really let that happen)
2 MB page size would reduce this to "just" 11k page faults per second.
I mean I'm not complaining about TLB issues which large pages do better at for obvious reasons, but thrashing the TLB is likely to be a lot cheaper than reading too much from the disk.
edit: and there have been SPARC CPUs with memory controllers that can do 256GB pages
You seem to know quite a bit about this - just wondering - how does this work? The GPU can generate PCIe bus traffic to do RAM reads or writes, but how does it cause a page fault in the CPU? Is this some kind of IOMMU? Is there any place I can read more about this?
Another benefit is reduce CPU involvement. Textures are fundamentally stored on disk, and GPU needs to access that data for rendering. Before we would have the CPU use OS's filesystem storage stack, read a file block, decode the texture in CPU memory, copy the texture to GPU memory using PCI-e, and ask the GPU to render with that data. This method allows the GPU directly read from a SSD, bypassing all of the steps in between. As SSD becomes faster and faster, OS's filesystem is becoming the bottleneck.