Messages in this thread | | | Date | Tue, 21 Mar 2000 11:35:15 -0800 (PST) | From | David Whysong <> | Subject | Re: Overcomittable memory |
| |
On 21 Mar 2000, Rask Ingemann Lambertsen wrote: >Den 20-Mar-00 21:04:35 skrev James Sutherland følgende om "Re: Overcomittable memory": >> On Mon, 20 Mar 2000 19:04:06 +0000, you wrote: > >>>I've seen this happen on several PCs, where all you do is malloc lots of >>>memory and fill it. It'll hard lock after a while. Yes, it's a bug, but... > >> So fix the bug, don't change the system to avoid showing it! > > The system _is_ the bug. Please tell me what is wrong with allocating a >piece of memory and using it? Nothing, of course. Yet Linux will currently >nuke the process (or another completely unrelated process) for doing that.
No, the bug is that you tried to use more memory than your computer has.
"Doctor, it hurts when I do this." Doctor: "Then don't do that."
You always accomplish more work with overcommit than without it.
The kernel policy for nuking processes when OOM is arguably broken, but that's a separate issue.
Dave
David Whysong dwhysong@physics.ucsb.edu Astrophysics graduate student University of California, Santa Barbara My public PGP keys are on my web page - http://www.physics.ucsb.edu/~dwhysong DSS PGP Key 0x903F5BD6 : FE78 91FE 4508 106F 7C88 1706 B792 6995 903F 5BD6 D-H PGP key 0x5DAB0F91 : BC33 0F36 FCCD E72C 441F 663A 72ED 7FB7 5DAB 0F91
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |