[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <40a4ed590904270748x7630ce79rd1e1c82b8fabb38e@mail.gmail.com>
Date: Mon, 27 Apr 2009 16:48:25 +0200
From: Zeno Davatz <zdavatz@...il.com>
To: Greg Stark <gsstark@....edu>
Cc: David Rientjes <rientjes@...gle.com>, linux-kernel@...r.kernel.org,
Hannes Wyss <hwyss@...see.com>
Subject: Re: Kernel 2.6.29 runs out of memory and hangs.
On Mon, Apr 27, 2009 at 3:35 PM, Greg Stark <gsstark@....edu> wrote:
> On Sun, Apr 26, 2009 at 8:55 PM, David Rientjes <rientjes@...gle.com> wrote:
>> There is work being done on a per-cgroup lowmem notifier which would allow
>> userspace to poll() on a device file and be notified of low memory
>> situations so that it can react on its own (like killing a low priority
>> task, expanding a cpuset, increasing a memcontroller limit, etc.)
>
> Surely anything that important ought to be running with overcommit
> disabled anyways.
Ok, I tried this suggestion as well. I done:
echo 2 > /proc/sys/vm/overcommit_memory
echo 0 > /proc/sys/vm/overcommit_ratio (Note: our system does not have
any swap, just 32 GB of memory).
Then I tried to run "htop" and got
bash: fork: Cannot allocate memory
I also tried it with
echo 1 > /proc/sys/vm/overcommit_ratio
Same result.
Best
Zeno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists