Messages in this thread Patch in this message | | | From | "Al Boldi" <> | Subject | RE: Kswapd flaw | Date | Wed, 29 Jun 2005 07:53:14 +0300 |
| |
Marcelo wrote: { On Tue, Jun 28, 2005 at 11:00:14PM +0300, Al Boldi wrote: > 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
--- linux-2.4.30/mm/mmap.c.orig 2005-06-28 17:15:27.000000000 -0300 +++ linux-2.4.30/mm/mmap.c 2005-06-28 17:15:29.000000000 -0300 @@ -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;
> 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.
- 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/
| |