Re: Setting memory allocators for library functions.

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Peter Seebach writes
:
>In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>>Malloc() does not overcommit - the kernel does. Malloc() doesn't know
>>and doesn't care.
>
>But it could still probably force the behavior.
>
>>None of these solutions are portable, however;
>
>Well, no, but the sole available definition of "portable" says that it is
>"portable" to assume that all the memory malloc can return is really
>available.

No, this is not a guarantee.

We also don't guarantee that you can read a file just because you
managed to open it (disk errors, nfs servers going away, forced
unmounts).

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message