Stephen C. Tweedie writes the following:
>
>It doesn't really help. You can implement it, sure, but only by
>returning an unconditional ENOMEM if there is any risk of going over
>budget.
>
>Your user space app uses all the memory it can and then gets ENOMEM on
>the next malloc. Fine.
>
>Then named does a malloc. It gets ENOMEM and dies, and the freed memory
>gets gobbled by your memory-hog application. Then inetd does a malloc.
>It gets ENOMEM and dies. Then sendmail. Then init.
Why do you assume ENOMEM results in death? The whole point is that it doesn't
need to. Critical processes like init can sleep and retry after ENOMEM.
-
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 : Tue Mar 07 2000 - 21:00:21 EST