hxge Driver Configuration Parameters - Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module User's Guide

`hxge` Driver Configuration Parameters

The actual list of hxge driver parameters is subject to change from release to release. The following table lists the driver configuration parameters for the version 0.0.9 hxge driver. The table also lists the accepted values and defaults for the parameter, where applicable.

Table 7 Driver Configuration Parameters

Parameter	Description	Values	Default
`enable_jumbo`	Controls `hxge` driver runtime support of jumbo frames. `hxge` jumbo frame support is automatically enabled as needed (depending on the network interface-specified MTU value).	0 = No 1 = Yes	Automatic
`intr_type`	Controls what sort of interrupt mechanism (if any) is selected by the `hxge` driver. The `hxge` driver will automatically select the best (highest potential performance) interrupt support mechanism when it is initially loaded and started.	0 = INTx 1 = MSI 2 = MSIx 3 = Polling	Determined by system hardware support (MSIx is "best").
`rbr_entries`	Specifies how many 4KB receive buffers the hxge driver will allocate per receive channel (the NEM supports four parallel independent receive channels).		4096
`rcr_entries`	Specifies how many receive pointers (effectively, packets; jumbo packets can require up to 3 RCR entries per single jumbo packet) the `hxge` driver will allocate per receive channel.		8192
`rcr_timeout`	Magic internal unitless number. Do not change this number unless told to by a qualified Sun agent.
`rcr_threshold`	Magic internal unitless number. Do not change this number unless told to by a qualified Sun agent.
`rx_dma_channels`	Specifies how many receive DMA channels the `hxge` driver should attempt to activate when the driver is initialized and brought online. Each DMA channel represents an independent receive processing stream (interrupt and CPU with separate dedicated buffer pool, system resources permitting) capability.	1 = minimum 4 = maximum	4
`tx_dma_channels`	Specifies how many transmit DMA channels the hxge driver should attempt to activate when the driver is initialized and brought online.	1 = minimum 4 = maximum	4
`num_tx_descs`	Specifies how many transmit descriptors the `hxge` driver should allocate per transmit channel. Each transmit packet requires a transmit descriptor.		1024
`tx_buffer_size`	Specifies the small transmit buffer size. For transmit packets smaller than this value, the `hxge` driver will coalesce all the packet fragments together into a single pre-allocated `tx_buffer_size` `hxge` buffer; for transmit packets larger than this size, the `hxge` driver will construct a scatter/gather pointer list for the hardware to decipher.		256
`tx_mark_ints`	Magic internal unitless number. Do not change this number unless told to by a qualified Sun agent.
max_rx_pkts	Specifies the maximum number of receive packets (queued by the NEM network engine) will be processed on any one receive interrupt, before the `hxge` driver (interrupt service routine) will dismiss the interrupt, releasing the interrupted CPU to perform other actions.		64
vlan_id	Specifies the implicit VLAN ID that the `hxge` driver will assign to non-VLAN-tagged packets.		4094
debug	Controls `hxge` printout verbosity of `hxge` driver progress, actions, and events. Normally, only significant or serious (error) information is printed out. Note: Read Troubleshooting the Driver before changing this parameter.	0x2002 = normal operation (don’t print DBG messages) 0x2001 = debug operation (print debug messages)	2002
`strip_crc`	Controls whether the `hxge` driver or the NEM network engine strips off the packet CRC.	0 = disable 1 = enable	0
`enable_vmac_ints`	Controls whether or not the `hxge` driver enables VMAC interrupts.	0 = disable 1 = enable	0
`promiscuous`	Controls whether or not the `hxge` driver enables the NEM engine to run in promiscuous mode.	0 = disable 1 = enable	0
`chksum`	Controls whether or not the `hxge` driver enables the NEM engine hardware checksumming capability.	0 = no hardware checksumming, 1 = hardware receive packet checksumming 2 = hardware transmit checksumming 3 = both	3
`tcam`	Controls whether or not the `hxge` driver enables the Virtualized M2 NEM ASIC hardware engine, spreading the receive traffic across multiple (up to 4) parallel independent receive streams (interrupts, CPUs). This might also be referred to as DMA channel spreading. See also `rx_dma_channels` in this table.	0 = disable 1 = enable	1
`tcam_seed`	Magic internal unitless number. Do not change this number unless told to by a qualified Oracle agent.
`tcam_tcp_ipv4`	Controls whether or not the hxge driver enables DMA channel spreading for IPv4 UDP traffic.	0 = disable 1 = enable	1

Skip Navigation Links
Exit Print View
	Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module User's Guide Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module Documentation Library