> In my case (virtualization) I want to test/profile guest under heavy swapping > of a guests memory, so I intentionally create memory shortage by creating > guest much large then host memory, but I want system to swap out only > guest's memory. So this isn't an API question this is an obscure corner case testing question. > > > > > It would be probably useful if you could point us to the application > > source code that actually wants this feature. > > > This is two line patch to qemu that calls mlockall(MCL_CURRENT|MCL_FUTURE) > at the beginning of the main() and changes guest memory allocation to > use MAP_UNLOCKED flag. All alternative solutions in this thread suggest > that I should rewrite qemu + all library it uses. You see why I can't > take them seriously? And you want millions of users to have kernels with weird extra functions whole sole value is one test environment you wish to run See why we can't take you seriously either ? -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
