rlim_fd_max
The following section changed for releases prior to the Solaris 9 release.
| Default | 1024
to:
| | Default | 65,536
|
segkpsize
The following section changed for the Solaris 9 8/03 release. This section
was also moved to the General Parameters section of Chapter 2, Solaris Kernel Tunables.
| Units | Mbytes
to
| | Units | 8-Kbyte pages
|
segspt_minfree
The following section changed.
| Range | 0 to 32,767
to:
| | Range | 0 to 50% of physical memory.
|
shmsys:shminfo_shmseg
The following section changed.
| Description | Limit on the number
of shared memory segments that any one process can create.
to:
| | Description | Limit on the number
of shared memory segments that any one process can attach.
|
shmsys:shminfo_shmmax
The following sections changed.
| Description | Maximum size of system
V shared memory segment that can be created. This parameter is an upper limit
that is checked before the system sees if it actually has the physical resources
to create the requested memory segment.
to:
| | Description | Maximum size of system
V shared memory segment that can be created. This parameter is an upper limit
that is checked before the system sees if it actually has the physical resources
to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose
size is larger than the specified value will fail with an EINVAL error.
|
| Default | 1,048,576
to:
| | Default | 8,388,608
|
The following sections changed in the Solaris 9 8/03
release.
| Description | Maximum size of system
V shared memory segment that can be created. This parameter is an upper limit
that is checked before the system sees if it actually has the physical resources
to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose
size is larger than the specified value will fail with an EINVAL error.
to
| | Description | Maximum size of system
V shared memory segment that can be created. This parameter is an upper limit
that is checked before the application sees if it actually has the physical
resources to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose
size is larger than the specified value will fail with an EINVAL error.
This parameter specifies only the largest value the operating system
can accept for the size of a shared memory segment. Whether the segment can
be created depends entirely on the amount of swap space available on the system
and, for a 32-bit process, whether there is enough space available in the
process's address space for the segment to be attached.
| | Range | 0 - MAXINT on 32-bit systems,
0 - MAXINT64 on 64-bit systems
to
| | Range | 0 - MAXUINT32 on 32-bit systems,
MAXUINT64 on 64-bit systems
|
sq_max_size
| Range | 1 to 0 (unlimited)
to
| | Range | 0 (unlimited) to MAXINT
| | When to Change | When NCA is running
on a system with a lot of memory, increase this parameter to allow drivers
to queue more packets of data. If a server is under heavy load, increase this
parameter so modules and drivers may process more data without dropping
packets or getting backlogged.
to
| | When to Change | When NCA is running
on a system with a lot of memory, increase this parameter to allow drivers
to queue more packets of data. If a server is under heavy load, increase this
parameter so modules and drivers may process more data without dropping
packets or getting backlogged.
Note - sq_max_size=0 is intended only for benchmarks
or testing environments.
Solaris 8 and later releases -
Do not set this parameter to 0 on production systems. If you need to change
this parameter, gradually increase this value and monitor the system.
Solaris 7 and earlier releases -
Do not set this parameter to 0 on production systems. If you need to change
this parameter, gradually increase this value to a maximum of 100, and monitor
the system.
|
tmpfs:tmpfs_maxkmem
The following section changed.
| Default | to:
| | Default | One page or 4% of physical
memory, whichever is greater.
|
tmpfs:tmpfs_minfree
This parameter was corrected. The following section changed:
|
Previous