Shouldn't there be a threshold where mlock will fail?
Or are you saying that in general mlocking lots of memory will screw the
VM?
> But if you've mlock()ed enough to clog up the inactive
> list, the VM could just move the pages it cannot free
> back to the active list and it will come across those
> pages which are freeable eventually.
>
> Note that the maximum amount of mlock()ed memory is way
> higher than the maximum amount of pages the system puts
> on the inactive list.
>
> (at least, it was last I looked at the maximum number
> of mlocked pages)
>
> regards,
>
> Rik
> --
> IA64: a worthy successor to the i860.
>
> http://www.surriel.com/
> http://www.conectiva.com/ http://distro.conectiva.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-- Rick (rick@kuroyi.net) http://dxr3.sourceforge.netI think the slogan of the fansubbers puts it best: "Cheaper than crack, and lots more fun." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/