I was thinking that part of the page description for each texture could contain information wrt scaling, compression etc. I think the only issue is that you might want a smaller page size than you get in a typical system tlb, although there are ways around that...
If its done as a true page based system you only load the pages that you access, but yep, I guess sparse access could still present a problem, although you can always page out again. The paging of data in and out of disk is more of a OS issue. I have looked at the idea of the driver maintaining its own private paging file, but without OS support there's some minor issues to sort out.
John
Can you upload partial textures/mipmaps though? (And is the virtual memory system flexible enough to allow void parts?) If not big sparse textures (think 1024^3 3D textures) would still present a huge problem, even if you could virtualize unused parts all the way back to the HD via system virtual memory after loading (can you do that?).
If its done as a true page based system you only load the pages that you access, but yep, I guess sparse access could still present a problem, although you can always page out again. The paging of data in and out of disk is more of a OS issue. I have looked at the idea of the driver maintaining its own private paging file, but without OS support there's some minor issues to sort out.
John