lkml.org 
[lkml]   [2000]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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/

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