Clarify M_MMAP_THRESHOLD

Clarify M_MMAP_THRESHOLD

[Andreas Jaeger]

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@suse.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
-@code{free}.
+@code{free}.  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@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Clarify M_MMAP_THRESHOLD

[Andreas Schwab]

Andreas Jaeger <aj@suse.de> writes:

|> 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@suse.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
|> -@code{free}.
|> +@code{free}.  Note that requests smaller than this threshold might still
|> +bet allocated via @code{mmap}.
    ^^^
Typo.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Clarify M_MMAP_THRESHOLD

[Wolfram Gloger]

> We got a little bit confused on the purpose of M_MMAP_THRESHOLD and I
> think it should be explained better in the manual.

> --- 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
> -@code{free}.
> +@code{free}.  Note that requests smaller than this threshold might still
> +bet allocated via @code{mmap}.
   ^^^ be
>  @item M_MMAP_MAX
>  The maximum number of chunks to allocate with @code{mmap}.  Setting this
>  to zero disables all use of @code{mmap}.

Definitely ok with typo fix.

Regards,
Wolfram.