Messages in this thread | | | Date | Wed, 6 Jun 2007 19:15:53 -0400 (EDT) | From | Justin Piszcz <> | Subject | Re: [PATCH] trim memory not covered by WB MTRRs |
| |
On Wed, 6 Jun 2007, Randy Dunlap wrote:
> On Wed, 6 Jun 2007 18:54:37 -0400 (EDT) Justin Piszcz wrote: > >> Hm, not sure if it was from the patch or what but I ran this: >> >> 1. swapoff -a >> 2. ./eatmem >> > > You usually have to access the allocated memory, like: > > *d = 1.0; > > for it to actually be allocated (AFAIK). > >> } >> >> return 0; >> } >> >> Any idea why the OOM killer can or does not kill it? > > What are the values of /proc/sys/vm/overcommit* ? > > See Documentation/vm/overcommit-accounting .
They should be the defaults as I do not change them:
p34:~# find /proc/|grep -i overcommit /proc/sys/vm/overcommit_memory /proc/sys/vm/overcommit_ratio find: /proc/5128: No such file or directory p34:~# cat /proc/sys/vm/overcommit_memory 0 p34:~# cat /proc/sys/vm/overcommit_ratio 50 p34:~#
Comments? - 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/
| |