Linux Driver Software: Broadcom NetXtreme II® Network Adapter User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtremeII/English/linux.htm[9/5/2014 3:45:01 PM]
(TPA) feature. By default, the driver will aggregate TCP packets. Use disable_tpa to disable the advanced TPA feature.
Set the
disable_tpa
parameter to 1 as shown below to disable the TPA feature on all NetXtreme II network adapters in the
system. The parameter can also be set in modprobe.conf. See the man page for more information.
insmod bnx2x.ko disable_tpa=1
or
modprobe bnx2x disable_tpa=1
int_mode
The
int_mode
parameter is used to force using an interrupt mode.
Set the
int_mode
parameter to 1 to force using the legacy INTx mode on all NetXtreme II adapters in the system.
insmod bnx2x.ko int_mode=1
or
modprobe bnx2x int_mode=1
Set the
int_mode
parameter to 2 to force using MSI mode on all NetXtreme II adapters in the system.
insmod bnx2x.ko int_mode=2
or
modprobe bnx2x int_mode=2
Set the
int_mode
parameter to 3 to force using MSI-X mode on all NetXtreme II adapters in the system.
dropless_fc
The
dropless_fc
parameter can be used to enable a complementary flow control mechanism on BCM57711/BCM57712
adapters. The default flow control mechanism is to send pause frames when the on-chip buffer (BRB) is reaching a certain
level of occupancy. This is a performance targeted flow control mechanism. On BCM57711/BCM57712 adapters, one can
enable another flow control mechanism to send pause frames, where one of the host buffers (when in RSS mode) are
exhausted.
This is a "zero packet drop" targeted flow control mechanism.
Set the
dropless_fc
parameter to 1 to enable the dropless flow control mechanism feature on all BCM57711/BCM57712
NetXtreme II adapters in the system.
insmod bnx2x.ko dropless_fc=1
or
modprobe bnx2x dropless_fc=1
disable_iscsi_ooo
The
disable_iscsi_ooo
parameter
is to disable the allocation of the iSCSI TCP Out-of-Order (OOO) reception resources,
specifically for VMware for low-memory systems.
multi_mode
The optional parameter
multi_mode
is for use on systems that support multi-queue networking. Multi-queue networking on
the receive side depends only on MSI-X capability of the system, multi-queue networking on the transmit side is supported
only on kernels starting from 2.6.27. By default,
multi_mode
parameter is set to 1. Thus, on kernels up to 2.6.26, the driver
will allocate on the receive side one queue per-CPU and on the transmit side only one queue. On kernels starting from 2.6.27,
the driver will allocate on both receive and transmit sides, one queue per-CPU. In any case, the number of allocated queues
will be limited by number of queues supported by hardware.
The
multi_mode
optional parameter can also be used to enable SAFC (Service Aware Flow Control) by differentiating the
traffic to up to 3 CoS (Class of Service) in the hardware according to the VLAN PRI value or according to the IP DSCP value
(least 3 bits).
num_queues
The optional parameter
num_queues
may be used to set the number of queues when
multi_mode
is set to 1 and interrupt
