DragonFly kernel List (threaded) for 2005-02
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: phk malloc, was (Re: ptmalloc2)
On Sat, 26 Feb 2005 14:27:13 -0500
Gary Thorpe <gathorpe79@xxxxxxxxx> 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?
-Chris
- References:
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
- Re: phk malloc, was (Re: ptmalloc2)
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]