Skip to contentSkip to conversation

Kswapd flaw

DISCUSSION Al Boldi 1 participant 1 message Jun 29, 2005 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

Al Boldi

author
#1 lore raw
In reply to a message not in the archive

Marcelo wrote: {

Quoted 7 lines · Al Boldi

Hi,
I read Documentation/vm/overcommit-accounting, thank you! It's for 2.6. Values are 0,1,2. What is needed is 2.
In 2.4 values are 0,1. What is needed is 0, which is default, which is the problem.
Kswapd overcommits anyway.
Can this be fixed/adjusted?

Can you please try this

mm/mmap.c 2005-06-28 17:15:29.000000000 -0300 renamed from mm/mmap.c.orig 2005-06-28 17:15:27.000000000 -0300 +1 -1
@@ -70,7 +70,7 @@
            return 1;
 
        /* The page cache contains buffer pages these days.. */
-       free = page_cache_size;
+//     free = page_cache_size;
        free += nr_free_pages();
        free += nr_swap_pages;
 
Quoted 2 lines

CONFIG_OOM_KILLER does not disable/enable OOM-Killer. It merely selects a different style of killing.

What you mean? What happens if you disable CONFIG_OOM_KILLER? }

1. Thanks for the patch pointer. Can someone work on this?

2 .You only need OOM-Killer if you overcommit.