This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
We got a little bit confused on the purpose of M_MMAP_THRESHOLD and I think it should be explained better in the manual. Ok to commit the appended patch? Andreas 2003-02-24 Andreas Jaeger <aj at suse dot de> * manual/memory.texi (Malloc Tunable Parameters): Clarify behaviour of M_MMAP_THRESHOLD. ============================================================ Index: manual/memory.texi --- manual/memory.texi 22 Jul 2002 00:57:09 -0000 1.76 +++ manual/memory.texi 25 Feb 2003 05:26:43 -0000 @@ -697,7 +697,8 @@ heap size such that excessive amounts of All chunks larger than this value are allocated outside the normal heap, using the @code{mmap} system call. This way it is guaranteed that the memory for these chunks can be returned to the system on - at code{free} dot + at code{free} dot Note that requests smaller than this threshold might still +bet allocated via @code{mmap}. @item M_MMAP_MAX The maximum number of chunks to allocate with @code{mmap}. Setting this to zero disables all use of @code{mmap}. -- Andreas Jaeger SuSE Labs aj at suse dot de private aj at arthur dot inka dot de http://www.suse.de/~aj
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |