In article <linux.kernel.Pine.LNX.4.10.10003130335020.30199-100000@sal.physics.ucsb.edu>,
David Whysong <dwhysong@physics.ucsb.edu> wrote:
>On 13 Mar 2000, Rask Ingemann Lambertsen wrote:
>>
>>Apps would be told that the system is out of memory instead of just
>>getting a SIGKILL'ed out of the blue sky. Apps getting NULL from
>>malloc() can react appropriately, such as saving your files to disk,
>>trying again a little later or just exiting if that is acceptable for
>>what the app was doing. Apps getting SIGKILL will take your unsaved work
>>with them in the fall.
>
>Ok, so my big gravitational simulation gets NULL from malloc and decides
>to save it's work and exit. Uh-oh, time to demand-load a page of
>executable code that had been discarded,
Discarded? But that would be overcommit -- if your system is running
without overcommit, there has to be a space for that page someplace
in core, and it shouldn't be blown away, no matter how frantically
the kernel may want to use that page for something else.
____
david parsons \bi/ Out, out, damned page!
\/
-
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/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:26 EST