Skip to contentSkip to conversation

OOM killer???

DISCUSSION Jesse Pollard 1 participant 1 message Mar 29, 2001

lore
Share & tools
lore
#0 lore raw

Guest section DW <[email protected]>:

Quoted 9 lines · Sean Hunter
Quoted 4 lines

The reason the aero engineers don't need to select a passanger to throw out when the plane is overloaded is simply that the plane operators do not allow the plane to become overloaded.

Yes. But today Linux willing overcommits. It would be better if the default was not to.

Preferably, the default should be a configure option, with runtime alterations.

Quoted 7 lines
Quoted 4 lines

Furthermore, why do you suppose an aeroplane has more than one altimeter, artifical horizon and compass? Do you think it's because they are unable to make one of each that is reliable? Or do you think its because they are concerned about what happens if one fails _however unlikely that is_.

Unix V6 did not overcommit, and panicked if is was out of swap because that was a cannot happen situation.

Ummm... no. The user got "ENOMEM" or "insufficient memory for fork", or "swap error". The system didn't panic unless there was an I/O error on the swap device.

Quoted 2 lines

If you argue that we must design things so that there is no overcommit and still have an OOM killer just in case, I have no objections at all.

good.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]

Any opinions expressed are solely my own.