[lkml]   [2000]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Avoiding OOM on overcommit...?
> The explanation is not the issue. The issue is having programs that
> act correctly (check malloc() returns, don't follow null pointers,
> etc.) fail in ways that are quite difficult for their programmers
> to prevent.

Indeed. And its completely valid to kill them off. Right now nobody has
a serious commercial requirement for non-overcommit on Linux.

> For example, this implies one should not run a production database on
> a multi-user Linux machine since it could crash in non-recoverable
> ways.

Database people don't care. Firstly you dont run the machine out of memory.
Secondly their data has to be robust against people tripping over the
power cord which is probably the more common event.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:57    [W:0.112 / U:3.248 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site