-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Feb 26, 2005, at 6:28 PM, Chris Pressey wrote:
>> And the point we keep coming back to is that it is impossible for an
>> application to accurately self regulate its resource usage (unless you
>> mean allowing command line flags to specify how much memory to use
>> [why not just set rlimits instead]) since it does not receive
>> accurate feedback from the kernel when over commit is allowed.
>
> man mlock(1):
>
> [EAGAIN] Locking the indicated range would exceed either the
> system or per-process limit for locked memory.
>
> Is that not accurate feedback?
>
Read more closely: "limit for __locked__ memory". The limits don't have
to be (and frequently aren't) the same.
- --
Tobias DiPasquale
7A79 308C 0354 EA9C 7807 ED83 03C9 9E01 148E 7D01
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (Darwin)
iD8DBQFCIRU9A8meARSOfQERAnZCAKCba2kparU0DoiIoW6K09Git3mh3wCg4VdG
aFVFIKbcNqKM07knqydE1x0=
=QRvT
-----END PGP SIGNATURE-----