From patchwork Sat Dec 31 15:40:31 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Siddhesh Poyarekar X-Patchwork-Id: 709934 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3trSHQ0N39z9t0m for ; Sun, 1 Jan 2017 02:41:21 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.b="jvp1Vrhv"; dkim-atps=neutral DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:date:message-id:in-reply-to :references; q=dns; s=default; b=hlAm5WsJKGCx9oAMcjvnxs0gCNy0PLF pqIW4dNl7Q/C8RDAhp425con8jp+rEfSwodzIqL/6NmGqFwTyXBZih3jV11dMT1j cEHvN0WNbOwzzirpf4X0ZvBBuGxRa07rECtgepijUBlIHlX0DOUeDiMMyCdBQE1b igEVe7JUGC9A= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:date:message-id:in-reply-to :references; s=default; bh=P5ByKMR+mZ2hWOJxwmi3qZ8+eVg=; b=jvp1V rhvyR/sI7f3Za1TRgZf0Daz5Mhi70lMKF34/n+7EW14vE7sWgJmlqTsP3iI5KWHA ulNYBxtq0Un+m0eVlala0rwDEk+VDAZUClgNFp4CvS8SIeJ+qEsxOnkPgN757PCu KYjWKfAExLENq/wWWnHI+W2iUpVbTtsprlM8Ms= Received: (qmail 115232 invoked by alias); 31 Dec 2016 15:41:04 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Delivered-To: mailing list libc-alpha@sourceware.org Received: (qmail 115171 invoked by uid 89); 31 Dec 2016 15:41:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL, BAYES_50, RCVD_IN_DNSWL_NONE, SPF_NEUTRAL autolearn=no version=3.3.2 spammy=conducted, arena, Abort, vary X-HELO: homiemail-a119.g.dreamhost.com From: Siddhesh Poyarekar To: libc-alpha@sourceware.org Cc: fweimer@redhat.com, carlos@redhat.com Subject: [PATCH 4/4] User manual documentation for tunables Date: Sat, 31 Dec 2016 21:10:31 +0530 Message-Id: <1483198831-2232-5-git-send-email-siddhesh@sourceware.org> In-Reply-To: <1483198831-2232-1-git-send-email-siddhesh@sourceware.org> References: <1483198831-2232-1-git-send-email-siddhesh@sourceware.org> Create a new node for tunables documentation and add notes for the malloc tunables. * manual/tunables.texi: New chapter. * manual/Makefile (chapters): Add it. * manual/probes.texi (@node): Point to the Tunables chapter. --- manual/Makefile | 3 +- manual/probes.texi | 2 +- manual/tunables.texi | 192 +++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 195 insertions(+), 2 deletions(-) create mode 100644 manual/tunables.texi diff --git a/manual/Makefile b/manual/Makefile index f2f694f..ecc2bf6 100644 --- a/manual/Makefile +++ b/manual/Makefile @@ -38,7 +38,8 @@ chapters = $(addsuffix .texi, \ message search pattern io stdio llio filesys \ pipe socket terminal syslog math arith time \ resource setjmp signal startup process ipc job \ - nss users sysinfo conf crypt debug threads probes) + nss users sysinfo conf crypt debug threads \ + probes tunables) add-chapters = $(wildcard $(foreach d, $(add-ons), ../$d/$d.texi)) appendices = lang.texi header.texi install.texi maint.texi platform.texi \ contrib.texi diff --git a/manual/probes.texi b/manual/probes.texi index 237a918..eb91c62 100644 --- a/manual/probes.texi +++ b/manual/probes.texi @@ -1,5 +1,5 @@ @node Internal Probes -@c @node Internal Probes, , POSIX Threads, Top +@c @node Internal Probes, Tunables, POSIX Threads, Top @c %MENU% Probes to monitor libc internal behavior @chapter Internal probes diff --git a/manual/tunables.texi b/manual/tunables.texi new file mode 100644 index 0000000..ac8c38f --- /dev/null +++ b/manual/tunables.texi @@ -0,0 +1,192 @@ +@node Tunables +@c @node Tunables, , Internal Probes, Top +@c %MENU% Tunable switches to alter libc internal behavior +@chapter Tunables +@cindex tunables + +@dfn{Tunables} are a feature in @theglibc{} that allows application authors and +distribution maintainers to alter the runtime library behavior to match +their workload. These are implemented as a set of switches that may be +modified in different ways. The current default method to do this is via +the @env{GLIBC_TUNABLES} environment variable by setting it to a string +of colon-separated @var{name}=@var{value} pairs. For example, the following +example enables malloc checking and sets the malloc trim threshold to 128 +bytes: + +@example +GLIBC_TUNABLES=glibc.malloc.trim_threshold=128:glibc.malloc.check=3 +export GLIBC_TUNABLES +@end example + +Tunables are not part of the @glibcadj{} stable ABI, and they are +subject to change or removal across releases. Additionally, the method to +modify tunable values may change between releases and across distributions. +It is possible to implement multiple `frontends' for the tunables allowing +distributions to choose their preferred method at build time. + +Finally, the set of tunables available may vary between distributions as +the tunables feature allows distributions to add their own tunables under +their own namespace. + +@menu +* Tunable names:: The structure of a tunable name +* Memory Allocation Tunables:: Tunables in the memory allocation subsystem +@end menu + +@node Tunable names +@section Tunable names +@cindex Tunable names +@cindex Tunable namespaces + +A tunable name is split into three components, a top namespace, a tunable +namespace and the tunable name. The top namespace for tunables implemented in +@theglibc{} is @code{glibc}. Distributions that choose to add custom tunables +in their maintained versions of @theglibc{} may choose to do so under their own +top namespace. + +The tunable namespace is a logical grouping of tunables in a single +module. This currently holds no special significance, although that may +change in the future. + +The tunable name is the actual name of the tunable. It is possible that +different tunable namespaces may have tunables within them that have the +same name, likewise for top namespaces. Hence, we only support +identification of tunables by their full name, i.e. with the top +namespace, tunable namespace and tunable name, separated by periods. + +@node Memory Allocation Tunables +@section Memory Allocation Tunables +@cindex memory allocation tunables +@cindex malloc tunables +@cindex tunables, malloc + +@deftp {Tunable namespace} glibc.malloc +Memory allocation behavior can be modified by setting any of the +following tunables in the @code{malloc} namespace: +@end deftp + +@deftp Tunable glibc.malloc.check +This tunable supersedes the @env{MALLOC_CHECK_} environment variable and is +identical in features. + +Setting this tunable enables a special (less efficient) memory allocator for +the malloc family of functions that is designed to be tolerant against simple +errors such as double calls of free with the same argument, or overruns of a +single byte (off-by-one bugs). Not all such errors can be protected against, +however, and memory leaks can result. The following list describes the values +that this tunable can take and the effect they have on malloc functionality: + +@itemize @bullet +@item @code{0} Ignore all errors. The default allocator continues to be in +use, but all errors are silently ignored. +@item @code{1} Report errors. The alternate allocator is selected and heap +corruption, if detected, is reported as diagnostic messages to @code{stderr} +and the program continues execution. +@item @code{2} Abort on errors. The alternate allocator is selected and if +heap corruption is detected, the program is ended immediately by calling +@code{abort}. +@item @code{3} Fully enabled. The alternate allocator is selected and is fully +functional. That is, if heap corruption is detected, a verbose diagnostic +message is printed to @code{stderr} and the program is ended by calling +@code{abort}. +@end itemize + +Like @env{MALLOC_CHECK_}, @code{glibc.malloc.check} has a problem in that it +diverges from normal program behavior by writing to @code{stderr}, which could +by exploited in SUID and SGID binaries. Therefore, @code{glibc.malloc.check} +is disabled by default for SUID and SGID binaries. This can be enabled again +by the system administrator by adding a file @file{/etc/suid-debug}; the +content of the file could be anything or even empty. +@end deftp + +@deftp Tunable glibc.malloc.top_pad +This tunable supersedes the @env{MALLOC_TOP_PAD_} environment variable and is +identical in features. + +This tunable determines the amount of extra memory in bytes to obtain from the +system when any of the arenas need to be extended. It also specifies the +number of bytes to retain when shrinking any of the arenas. This provides the +necessary hysteresis in heap size such that excessive amounts of system calls +can be avoided. + +The default value of this tunable is @samp{0}. +@end deftp + +@deftp Tunable glibc.malloc.perturb +This tunable supersedes the @env{MALLOC_PERTURB_} environment variable and is +identical in features. + +If set to a non-zero value, memory blocks are initialized with values depending +on some low order bits of this tunable when they are allocated (except when +allocated by calloc) and freed. This can be used to debug the use of +uninitialized or freed heap memory. Note that this option does not guarantee +that the freed block will have any specific values. It only guarantees that the +content the block had before it was freed will be overwritten. + +The default value of this tunable is @samp{0}. +@end deftp + +@deftp Tunable glibc.malloc.mmap_threshold +This tunable supersedes the @env{MALLOC_MMAP_THRESHOLD_} environment variable +and is identical in features. + +When this tunable is set, all chunks larger than this value in bytes 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}. Note that requests smaller than this threshold might still be +allocated via @code{mmap}. + +If this tunable is not set, the default value is set to @samp{131072} bytes and +the threshold is adjusted dynamically to suit the allocation patterns of the +program. If the tunable is set, the dynamic adjustment is disabled and the +value is set as static. +@end deftp + +@deftp Tunable glibc.malloc.trim_threshold +This tunable supersedes the @env{MALLOC_TRIM_THRESHOLD_} environment variable +and is identical in features. + +The value of this tunable is the minimum size (in bytes) of the top-most, +releasable chunk in an arena that will trigger a system call in order to return +memory to the system from that arena. + +If this tunable is not set, the default value is set as 128 KB and the +threshold is adjusted dynamically to suit the allocation patterns of the +program. If the tunable is set, the dynamic adjustment is disabled and the +value is set as static. +@end deftp + +@deftp Tunable glibc.malloc.mmap_max +This tunable supersedes the @env{MALLOC_MMAP_MAX_} environment variable and is +identical in features. + +The value of this tunable is maximum number of chunks to allocate with +@code{mmap}. Setting this to zero disables all use of @code{mmap}. + +The default value of this tunable is @samp{65536}. +@end deftp + +@deftp Tunable glibc.malloc.arena_test +This tunable supersedes the @env{MALLOC_ARENA_TEST} environment variable and is +identical in features. + +The @code{glibc.malloc.arena_test} tunable specifies the number of arenas that +can be created before the test on the limit to the number of arenas is +conducted. The value is ignored if @code{glibc.malloc.arena_max} is set. + +The default value of this tunable is 2 for 32-bit systems and 8 for 64-bit +systems. +@end deftp + +@deftp Tunable glibc.malloc.arena_max +This tunable supersedes the @env{MALLOC_ARENA_MAX} environment variable and is +identical in features. + +This tunable sets the number of arenas to use in a process regardless of the +number of cores in the system. + +The default value of this tunable is @code{0}, meaning that the limit on the +number of arenas is determined by the number of CPU cores online. For 32-bit +systems the limit is twice the number of cores online and on 64-bit systems, it +is 8 times the number of cores online. +@end deftp