Systemkennung Linux (firstname.lastname@example.org)
Mon, 18 Nov 1996 15:01:15 +0100 (MET)
> If the vm area is LOCKED in core e.g. for realtime purposes, it will touch
> any of the pages by reading a byte from them.
> IMHO, this is not strictly true, it should touch the pages by _writing_ ,
> as this makes a difference on zero pages:
> imagine a realtime process that has malloced a large chunk (with a mmap
> based malloc), mlocks it, and then uses it - if memory is tight, it will
> nevertheless cause swapping activity, which is what it wanted to prevent
> by mlocking it.
Writing isn't correct either in case of read-only pages. Solution is