Sounds like an awful amount work to bypass kernel caching and swapping to revert back to how things are without the virtual memory abstraction. I'd just start

Sounds like an awful amount work to bypass kernel caching and swapping to revert back to how things are without the virtual memory abstraction. I'd just start as the author described. Then, if and when I know that I know better than the kernel, I might implement some sort of userspace caching instead, proven that it won't hamper overall performance. I might just mlock critical btree nodes or indexes and still leave data blobs or less frequently used structures under vmem. Virtual memory is one of the things that surprisingly just works and does that without many drawbacks. I don't see the point of rejecting its offering straight off the bat.