Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11.1 Tunable Parameters Reference Manual Oracle Solaris 11.1 Information Library |
1. Overview of Oracle Solaris System Tuning
What's New in Oracle Solaris System Tuning?
Tuning an Oracle Solaris System
Tuning the Oracle Solaris Kernel
Example-Setting a Parameter in /etc/system
Recovering From an Incorrect Value
Example-Using mdb to Display Information
Special Oracle Solaris tune and var Structures
Viewing Oracle Solaris System Configuration Information
2. Oracle Solaris Kernel Tunable Parameters
3. Oracle Solaris ZFS Tunable Parameters
5. Internet Protocol Suite Tunable Parameters
A. Tunable Parameters Change History
The format for the description of each tunable parameter is as follows:
Parameter Name
Description
Data Type
Default
Range
Units
Dynamic?
Validation
Implicit
When to Change
Zone Configuration
Commitment Level
Change History
Is the exact name that is typed in the /etc/system file, or found in the /etc/default/facility file.
Most parameters names are of the form parameter where the parameter name does not contain a colon (:). These names refer to variables in the core portion of the kernel. If the name does contain a colon, the characters to the left of the colon reference the name of a loadable module. The name of the parameter within the module consists of the characters to the right of the colon. For example:
module_name:variable
Briefly describes what the parameter does or controls.
Indicates the signed or unsigned short integer or long integer. A long integer is twice the width in bits as an integer. For example, an unsigned integer = 32 bits, an unsigned long integer = 64 bits.
(Optional) Describes the unit type.
What the system uses as the default value.
Specifies the possible range allowed by system validation or the bounds of the data type.
MAXINT – A shorthand description for the maximum value of a signed integer (2,147,483,647)
MAXUINT – A shorthand description for the maximum value of an unsigned integer (4,294,967,295)
Yes, if the parameter can be changed on a running system with the mdb or kmdb debugger. No, if the parameter is a boot time initialization only.
Checks that the system applies to the value of the variable either as specified in the /etc/system file or the default value, as well as when the validation is applied.
(Optional) Provides unstated constraints that might exist on the parameter, especially in relation to other parameters.
Explains why someone might want to change this value. Includes error messages or return codes.
Identifies whether the parameter can be set in a exclusive-IP zone or must be set in the global zone. None of the parameters can be set in shared-IP zones.
Identifies the stability of the interface. Many of the parameters in this manual are still evolving and are classified as unstable. For more information, see attributes(5).
(Optional) Contains a link to the Change History appendix, if applicable.