Better test case timings: I changed from doing entire linear write testing to just touching the pages, to take memory bandwidth out of the equation. VirtualAlloc takes 0ms on 4k pages, 6ms on 2mb pages. Fault handling takes 60ms on 4k pages, 0ms on 2mb pages. So that's that.
-
-
That is assuming there are backwards compatibility reasons why you have to keep supporting 4k pages in "compatibility" mode, etc. - I can't honestly see there being a point to 4k pages for the normal case of modern apps that all use literally gigabytes of memory?
-
Also, paging is kind of for chumps anyway? Like, the OS probably has to support it, but you don’t actually want to be doing it ever, so, probably should not design for that as a primary use case.
- Show replies
New conversation -
-
-
A device driver may have locked pages for DMA. As my owner noted, you can create artificial pages, but you have to maintain the ruse consistently down to the driver level. And you can get most of the same effect via prefetch.https://devblogs.microsoft.com/oldnewthing/?p=105200 …
-
I still don't understand how this is relevant. With all 4k pages you still have the problem of locked pages, and have to pick a different page to evict if the one you were going to evict is locked. The rule would just be that if a 4k page is locked inside a 2mb page, it's locked.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.