Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
B.  Revision History for this Manual Changed Parameters rlim_fd_max  Previous   Contents   Next 
   
 

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

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:

Units

Bytes

to:

Units

Pages

tcp_rexmit_interval_max

The following section changed.

Range

1 millisecond to 20 seconds

to:

Range

1 millisecond to 2 hours

tcp_slow_start_initial

This parameter was corrected.

For information, see "tcp_slow_start_initial".

tcp_conn_req_max_q0

The following section changed:

When to Change

For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.

The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.

When a connection request is received, TCP first checks if the number (N) of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.

to:

When to Change

For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.

The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.

When a connection request is received, TCP first checks if the number of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum (N) for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.

Removal of sun4d Support

The sun4d platform is not supported in the Solaris 9 release. The following parameters were modified to reflect the removal of sun4d support:

  • max_nprocs

  • maxphys

  • noexec_user_stack

Changes to Existing Parameters From the Previous Release (Solaris 8)

shmsys:shminfo_shmmin

The following section changed:

 
 
 
  Previous   Contents   Next