Re: Virtual vs. physical swap & shared memory forks (clone)

From: Richard Gooch (rgooch@ras.ucalgary.ca)
Date: Sat Mar 25 2000 - 15:43:28 EST


Linda Walsh writes:
> > Removing overcommit might make malloc() return null, but that's only one
> > of a host of ways to allocate memory. The other methods don't have a
> > return value. So arguing that "overcommit is bad, because it breaks the
> > malloc() return value" is pointless.
>
> What other methods? calloc - ENOMEM, open <object>, ENOMEM, fork:
> ENOMEM. Etc. All what you would expect if there was NOMEM.

Stack "allocation". No error code available.

                                Regards,

                                        Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca

-
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 : Fri Mar 31 2000 - 21:00:26 EST