Skip to contentSkip to conversation

OOM killer

DISCUSSION Thomas Hood 5 participants 7 messages Sep 27, 2001 – Sep 28, 2001

lore
Share & tools
lore
#0 lore raw

After meeting the OOM killer for the first time (not a pleasant meeting) I went looking for info about it and read through some of the threads that took place on l-k a few months ago. I'm sure I didn't read everything, and I am far from being an expert in this area, but are my two cents anyway.

It is all very well to have a "smart" function that tries to minimize the damage done when the OS has to start killing processes in order to recover memory. However:

1) It's better if this situation doesn't arise in the first place, and,
2) once it does arise, it's better to let the administrator decide what to kill. Sometimes the administrator will get fired for killing the database and sometimes he'll get fired for killing Netscape--- there is no way for the authors of Linux to know in advance.

Some OSes don't allow memory overcommit at all. On these OSes, a process will simply fail if it tries to allocate memory that's not available. That Linux allows processes to go ahead under such circumstances can, I suppose, be called a 'feature'. But the result of that feature is that OOM can occur and then a kill decision has to be made. How this decision is made ought to be under the administrator's control.

How about assigning each process a property similar to its niceness which would be used to decide which process to kill in the event of OOM? Let's call this property 'humility'. By default, processes would run with humility zero. A process run with negative humility would never be allowed to proceed unless there was enough VM to back up its memory request. A process with non-negative humility would be allowed to proceed under such circumstances, but it would be taking the chance that it would be killed later.

So the system starts to run out of memory. If all processes have the same humility then the OOM-killer adjudicator is left to decide among them just as it does now. Those with negative humility will never be killed, and they will never have to be killed because all the memory they allocated really exists. Among remaining process, the humblest get killed first; among those equally humble, the baddest get killed.

So someday in the future I fire up my webserver and start Apache with negative humility since it's a mission-critical app. My boss logs in and starts writing e-mail (humility 0 process). There's memory pressure, so I take the precaution of starting Netscape with

    $ humble communicator
to make sure that communicator gets the axe if we run oom.

Your humble servant,
Thomas Hood

#1 lore raw
Quoted 3 lines · Thomas Hood

How about assigning each process a property similar to its niceness which would be used to decide which process to kill in the event of OOM?

Or maybe make it a configure option if Linux should over commit memory or not.
In some cases it would be nice if you could be sure that the memory you got was actually there, and for those cases you could build the kernel with CONFIG_NO_MEM_OVERCOMMIT (or something like that) so that linux would simply report ENOMEM when there's no more memory.

Best regards,
Jesper Juhl
[email protected]

#2 lore raw
Quoted 2 lines · --On Wednesday, 26 September, 2001 7:11 PM +0200 Jesper Juhl…

Or maybe make it a configure option if Linux should over commit memory or not.

deja vu

shed:~# cat /proc/sys/vm/overcommit_memory
0
shed:~# echo 1 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
1
shed:~# echo 0 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
0

--
Alex Bligh

#3 lore raw
In reply to Jesper Juhl
Quoted 8 lines · Alex Bligh - linux-kernel
shed:~# cat /proc/sys/vm/overcommit_memory
0
shed:~# echo 1 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
1
shed:~# echo 0 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
0

ahh, I see. Well, you live and learn ;)

I think I've got to do my research better before writing mails to lkml.

Best regards,
Jesper Juhl
[email protected]

#4 lore raw
Quoted 7 lines
Quoted 3 lines
shed:~# echo 0 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
0

ahh, I see. Well, you live and learn ;)

I think I've got to do my research better before writing mails to lkml.

In part.

The option you want is '2' which isnt implemented 8)

0 - I don't care
1 - Use heuristics to guesstimate avoiding overcommit

#5 lore raw
Quoted 9 lines · Alan Cox
Quoted 7 lines
Quoted 3 lines
shed:~# echo 0 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
0

ahh, I see. Well, you live and learn ;)

I think I've got to do my research better before writing mails to lkml.

Quoted 6 lines

In part.

The option you want is '2' which isnt implemented 8)

0 - I don't care
1 - Use heuristics to guesstimate avoiding overcommit

Thank you for that info :)

I wrote a small test program that allocated memory in increasingly larger chunks, and I saw no major difference with a setting of "0" or "1", it seemed both settings allowed my program to allocate exactely the same amount of mem before ENOMEM was returned (I can send the test program on request).

I'll be looking forward to a setting of "2" becomming available :)

Best regards
Jesper Juhl

#6 lore raw

have look at the following posting some time ago:
http://uwsg.iu.edu/hypermail/linux/kernel/0003.2/0303.html

greetings Thomas,

--

Quoted 39 lines · Jesper Juhl
Quoted 9 lines · Alan Cox
Quoted 7 lines
Quoted 3 lines
shed:~# echo 0 >/proc/sys/vm/overcommit_memory
shed:~# cat /proc/sys/vm/overcommit_memory
0

ahh, I see. Well, you live and learn ;)

I think I've got to do my research better before writing mails to lkml.

Quoted 6 lines

In part.

The option you want is '2' which isnt implemented 8)

0 - I don't care
1 - Use heuristics to guesstimate avoiding overcommit

Thank you for that info :)

I wrote a small test program that allocated memory in increasingly larger chunks, and I saw no major difference with a setting of "0" or "1", it seemed both settings allowed my program to allocate exactely the same amount of mem before ENOMEM was returned (I can send the test program on request).

I'll be looking forward to a setting of "2" becomming available :)

Best regards
Jesper Juhl

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/