Messages in this thread | | | Date | Tue, 6 Nov 2001 14:31:08 +0100 | From | Stephan von Krawczynski <> | Subject | Re: out_of_memory() heuristic broken for different mem configurations |
| |
On Tue, 6 Nov 2001 09:40:51 -0200 (BRST) Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> Well, yes, its seems to be just a wrong magic number for this > setup/workload.
Well, first time I read the code I thought that this will happen. Simply think of a _slow_ system with _lots_ of mem. Chances are high you cannot match the seconds-rule.
> Linus, any suggestion to "fix" that ?
How about this really stupid idea: oom means allocs fail, so why not simply count failed 0-order allocs, if one succeeds, reset counter. If a page is freed reset counter. If counter reaches <new magic number> then you're oom. No timing involved, which means you can have as much mem or as slow host as you like. It isn't even really interesting, if you have swap or not, because a failed 0-order alloc tells you whatever mem you have, there is surely not much left. I'd try about 100 as magic number.
> /proc tunable (eeek) ?
NoNoNo, please don't do that!
Regards, Stephan
- 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/
| |