On Fri, 2002-07-26 at 11:31, Pavel Machek wrote:
> In what scenario can "strict overcommit" kill?
When the kernel grabs over 50% of RAM. Remember that includes page
tables. I've seen the kernel taking 35% of RAM.
>
> > +4 - (NEW) paranoid overcommit. The total address space commit
> > + for the system is not permitted to exceed swap. The machine
> > + will never kill a process accessing pages it has mapped
> > + except due to a bug (ie report it!).
>
> ...and why is that scenario impossible on "paranoid overcommit"?
You are guaranteed user pages are either discardable or all fit in swap.
If you run out of memory the kernel itself runs out of allocation space
for any kernel owned page.
-
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/
This archive was generated by hypermail 2b29 : Tue Jul 30 2002 - 14:00:23 EST