Messages in this thread | | | Date | Sat, 25 Mar 2000 13:43:28 -0700 | From | Richard Gooch <> | Subject | Re: Virtual vs. physical swap & shared memory forks (clone) |
| |
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/
| |