mlock(1)

[Jeff Garzik]

How feasible is it to create an mlock(1) utility, that would allow 
priveleged users to execute a daemon such that none of the memory the 
daemon allocates will ever be swapped out?

ntp daemon does mlock(2) internally, for example, but IMHO this is 
really a policy decision that could be moved out of the app.

Unfortunately I am VM-ignorant as always ;-)

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/