[lkml]   [2000]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectOvercomittable memory (Was: Linux 2.2.15pre12)
Den 06-Mar-00 16:29:18 skrev Rik van Riel følgende om "Re: Linux 2.2.15pre12":

> Think about running a big simulation process that fork()s to
> exec() /bin/mail in order to email its status or a partial
> solution to the person that started the simulation.

> A big rendering process that fork()/exec()s lpr.

> Without overcommit you'd need to have the 500 MB of swap free
> that the big simulation is using, even though it'll only use
> 1 MB for the little process that's being exec()ed...

This doesn't mean that overcommit is a good idea. It just means that
fork()/exec() is not a good way of launching programs. Using overcommit to
cover up for fork()/exec() deficiencies is like redirecting compiler
warnings to /dev/null instead of fixing the code. The symptoms become less
visible but the problem remains. The problem could be solved by introducing
a new system call with the ability to start an external program as a new


| Rask Ingemann Lambertsen | E-mail: |
| Please do NOT Cc: to me or the | WWW: |
| mailing list. I am on the list.| "ThrustMe" on XPilot, ARCnet and IRC |
| Hard work may not kill me, but why take chances? |

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:57    [W:0.220 / U:1.512 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site