Solaris Tunable Parameters Reference Manual - SCN Research
Solaris Tunable Parameters Reference Manual - SCN Research
Solaris Tunable Parameters Reference Manual - SCN Research
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
When to Change<br />
Commitment Level<br />
Do not change the value. If more logical interfaces are<br />
required, you might consider increasing the value. However,<br />
recognize that this change might have a negative impact on<br />
IP’s performance.<br />
Unstable<br />
ip_strict_dst_multihoming and<br />
ip6_strict_dst_multihoming<br />
Description<br />
Determines whether a packet arriving on a non forwarding<br />
interface can be accepted for an IP address that is not explicitly<br />
configured on that interface. If ip_forwarding is enabled, or<br />
xxx:ip_forwarding for the appropriate interfaces is<br />
enabled, then this parameter is ignored, because the packet is<br />
actually forwarded.<br />
Refer to RFC 1122, 3.3.4.2.<br />
Default<br />
Range<br />
0 (loose multihoming)<br />
0 = Off (loose multihoming)<br />
1 = On (strict multihoming)<br />
Dynamic?<br />
When to Change<br />
Commitment Level<br />
Yes<br />
If a machine has interfaces that cross strict networking<br />
domains (for example, a firewall or a VPN node), set this<br />
parameter to 1.<br />
Unstable<br />
ip_multidata_outbound<br />
Description<br />
Enables the network stack to send more than one packet at one<br />
time to the network device driver during transmission.<br />
Enabling this parameter reduces the per-packet processing<br />
costs by improving host CPU utilization, network throughput,<br />
or both.<br />
The multidata transmit (MDT) feature is only effective for<br />
device drivers that support this feature.<br />
See also “tcp_mdt_max_pbufs” on page 153.<br />
Chapter 4 • Internet Protocol Suite <strong>Tunable</strong> <strong>Parameters</strong> 139
Change language