Re: 2.4.10 VM: what avoids from having lots of unwriteable inactive

Rik van Riel (riel@conectiva.com.br)
Tue, 25 Sep 2001 13:13:37 -0300 (BRST)


On Tue, 25 Sep 2001, Linus Torvalds wrote:
> On Tue, 25 Sep 2001, Rik van Riel wrote:
> > >
> > > swap_out() will deactivate everything it finds to be not-recently used,
> > > and that's how the inactive list ends up getting replenished.
> >
> > mlock()
>
> Hey, if you've mlock'ed more than your available memory, there's nothing
> the VM layer can do. Except maybe a nice printk("Kiss your *ss goodbye");

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/