On Thu, Sep 18, 2014 at 12:27 PM, Kerin Millar wrote:
>
> The need for the OOM killer stems from the fact that memory can be
> overcommitted. These articles may prove informative:
>
A big problem with Linux along these fronts is that we don't really
have good mechanisms for prioritizing memory us
You could also disable the overcommitment so that an app that ask for too much
memory will be denied (you know the possible NULL pointer malloc could return.
With overcommit, it will never return NULL whatever the memory status is.
Without this, all requested memory is really allocated, and mall
On 18/09/2014 16:48, James wrote:
Hello,
Out Of Memory seems to invoke mysterious processes that kill
such offending processes. OOM seems to be a common problem
that pops up over and over again within the clustering communities.
I would greatly appreciate (gentoo) illuminations on the OOM issu
Hello,
Out Of Memory seems to invoke mysterious processes that kill
such offending processes. OOM seems to be a common problem
that pops up over and over again within the clustering communities.
I would greatly appreciate (gentoo) illuminations on the OOM issues;
both historically and for folks
4 matches
Mail list logo
