brintos

brintos / linux-shallow public Read only

0
0
Text · 27.5 KiB · 694f23a Raw
785 lines · plain
1sysfs interface common for all infiniband devices2-------------------------------------------------3 4What:		/sys/class/infiniband/<device>/node_type5What:		/sys/class/infiniband/<device>/node_guid6What:		/sys/class/infiniband/<device>/sys_image_guid7Date:		Apr, 20058KernelVersion:	v2.6.129Contact:	linux-rdma@vger.kernel.org10Description:11		=============== ===========================================12		node_type:	(RO) Node type (CA, RNIC, usNIC, usNIC UDP,13				switch or router)14 15		node_guid:	(RO) Node GUID16 17		sys_image_guid:	(RO) System image GUID18		=============== ===========================================19 20 21What:		/sys/class/infiniband/<device>/node_desc22Date:		Feb, 200623KernelVersion:	v2.6.1724Contact:	linux-rdma@vger.kernel.org25Description:26		(RW) Update the node description with information such as the27		node's hostname, so that IB network management software can tie28		its view to the real world.29 30 31What:		/sys/class/infiniband/<device>/fw_ver32Date:		Jun, 201633KernelVersion:	v4.1034Contact:	linux-rdma@vger.kernel.org35Description:36		(RO) Display firmware version37 38 39What:		/sys/class/infiniband/<device>/ports/<port-num>/lid40What:		/sys/class/infiniband/<device>/ports/<port-num>/rate41What:		/sys/class/infiniband/<device>/ports/<port-num>/lid_mask_count42What:		/sys/class/infiniband/<device>/ports/<port-num>/sm_sl43What:		/sys/class/infiniband/<device>/ports/<port-num>/sm_lid44What:		/sys/class/infiniband/<device>/ports/<port-num>/state45What:		/sys/class/infiniband/<device>/ports/<port-num>/phys_state46What:		/sys/class/infiniband/<device>/ports/<port-num>/cap_mask47Date:		Apr, 200548KernelVersion:	v2.6.1249Contact:	linux-rdma@vger.kernel.org50Description:51 52		=============== ===============================================53		lid:		(RO) Port LID54 55		rate:		(RO) Port data rate (active width * active56				speed)57 58		lid_mask_count:	(RO) Port LID mask count59 60		sm_sl:		(RO) Subnet manager SL for port's subnet61 62		sm_lid:		(RO) Subnet manager LID for port's subnet63 64		state:		(RO) Port state (DOWN, INIT, ARMED, ACTIVE or65				ACTIVE_DEFER)66 67		phys_state:	(RO) Port physical state (Sleep, Polling,68				LinkUp, etc)69 70		cap_mask:	(RO) Port capability mask. 2 bits here are71				settable- IsCommunicationManagementSupported72				(set when CM module is loaded) and IsSM (set73				via open of issmN file).74		=============== ===============================================75 76 77What:		/sys/class/infiniband/<device>/ports/<port-num>/link_layer78Date:		Oct, 201079KernelVersion:	v2.6.3780Contact:	linux-rdma@vger.kernel.org81Description:82		(RO) Link layer type information (Infiniband or Ethernet type)83 84 85What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/symbol_error86What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_errors87What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_remote_physical_errors88What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_switch_relay_errors89What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/link_error_recovery90What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_xmit_constraint_errors91What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_contraint_errors92What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/local_link_integrity_errors93What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/excessive_buffer_overrun_errors94What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_xmit_data95What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_data96What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_xmit_packets97What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_rcv_packets98What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/unicast_rcv_packets99What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/unicast_xmit_packets100What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/multicast_rcv_packets101What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/multicast_xmit_packets102What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/link_downed103What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_xmit_discards104What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/VL15_dropped105What:		/sys/class/infiniband/<device>/ports/<port-num>/counters/port_xmit_wait106Date:		Apr, 2005107KernelVersion:	v2.6.12108Contact:	linux-rdma@vger.kernel.org109Description:110		**Errors info**:111 112		symbol_error: (RO) Total number of minor link errors detected on113		one or more physical lanes.114 115		port_rcv_errors : (RO) Total number of packets containing an116		error that were received on the port.117 118		port_rcv_remote_physical_errors : (RO) Total number of packets119		marked with the EBP delimiter received on the port.120 121		port_rcv_switch_relay_errors : (RO) Total number of packets122		received on the port that were discarded because they could not123		be forwarded by the switch relay.124 125		link_error_recovery: (RO) Total number of times the Port126		Training state machine has successfully completed the link error127		recovery process.128 129		port_xmit_constraint_errors: (RO) Total number of packets not130		transmitted from the switch physical port due to outbound raw131		filtering or failing outbound partition or IP version check.132 133		port_rcv_constraint_errors: (RO) Total number of packets134		received on the switch physical port that are discarded due to135		inbound raw filtering or failing inbound partition or IP version136		check.137 138		local_link_integrity_errors: (RO) The number of times that the139		count of local physical errors exceeded the threshold specified140		by LocalPhyErrors141 142		excessive_buffer_overrun_errors: (RO) This counter, indicates an143		input buffer overrun. It indicates possible misconfiguration of144		a port, either by the Subnet Manager (SM) or by user145		intervention. It can also indicate hardware issues or extremely146		poor link signal integrity147 148		**Data info**:149 150		port_xmit_data: (RO) Total number of data octets, divided by 4151		(lanes), transmitted on all VLs. This is 64 bit counter152 153		port_rcv_data: (RO) Total number of data octets, divided by 4154		(lanes), received on all VLs. This is 64 bit counter.155 156		port_xmit_packets: (RO) Total number of packets transmitted on157		all VLs from this port. This may include packets with errors.158		This is 64 bit counter.159 160		port_rcv_packets: (RO) Total number of packets (this may include161		packets containing Errors. This is 64 bit counter.162 163		link_downed: (RO) Total number of times the Port Training state164		machine has failed the link error recovery process and downed165		the link.166 167		unicast_rcv_packets: (RO) Total number of unicast packets,168		including unicast packets containing errors.169 170		unicast_xmit_packets: (RO) Total number of unicast packets171		transmitted on all VLs from the port. This may include unicast172		packets with errors.173 174		multicast_rcv_packets: (RO) Total number of multicast packets,175		including multicast packets containing errors.176 177		multicast_xmit_packets: (RO) Total number of multicast packets178		transmitted on all VLs from the port. This may include multicast179		packets with errors.180 181		**Misc info**:182 183		port_xmit_discards: (RO) Total number of outbound packets184		discarded by the port because the port is down or congested.185 186		VL15_dropped: (RO) Number of incoming VL15 packets dropped due187		to resource limitations (e.g., lack of buffers) of the port.188 189		port_xmit_wait: (RO) The number of ticks during which the port190		had data to transmit but no data was sent during the entire tick191		(either because of insufficient credits or because of lack of192		arbitration).193 194		Each of these files contains the corresponding value from the195		port's Performance Management PortCounters attribute, as196		described in the InfiniBand Architecture Specification.197 198 199What:		/sys/class/infiniband/<device-name>/hw_counters/lifespan200What:		/sys/class/infiniband/<device-name>/ports/<port-num>/hw_counters/lifespan201Date:		May, 2016202KernelVersion:	4.6203Contact:	linux-rdma@vger.kernel.org204Description:205		The optional "hw_counters" subdirectory can be under either the206		parent device or the port subdirectories or both. If present,207		there are a list of counters provided by the hardware. They may208		match some of the counters in the counters directory, but they209		often include many other counters. In addition to the various210		counters, there will be a file named "lifespan" that configures211		how frequently the core should update the counters when they are212		being accessed (counters are not updated if they are not being213		accessed). The lifespan is in milliseconds and defaults to 10214		unless set to something else by the driver. Users may echo a215		value between 0-10000 to the lifespan file to set the length216		of time between updates in milliseconds.217 218 219What:		/sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/ndevs/<gid-index>220Date:		November 29, 2015221KernelVersion:	4.4.0222Contact:	linux-rdma@vger.kernel.org223Description: 	The net-device's name associated with the GID resides224		at index <gid-index>.225 226What:		/sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/types/<gid-index>227Date:		November 29, 2015228KernelVersion:	4.4.0229Contact:	linux-rdma@vger.kernel.org230Description: 	The RoCE type of the associated GID resides at index <gid-index>.231		This could either be "IB/RoCE v1" for IB and RoCE v1 based GIDs232		or "RoCE v2" for RoCE v2 based GIDs.233 234 235What:		/sys/class/infiniband_mad/umad<N>/ibdev236What:		/sys/class/infiniband_mad/umad<N>/port237What:		/sys/class/infiniband_mad/issm<N>/ibdev238What:		/sys/class/infiniband_mad/issm<N>/port239Date:		Apr, 2005240KernelVersion:	v2.6.12241Contact:	linux-rdma@vger.kernel.org242Description:243		Each port of each InfiniBand device has a "umad" device and an244		"issm" device attached. For example, a two-port HCA will have245		two umad devices and two issm devices, while a switch will have246		one device of each type (for switch port 0).247 248		======= =====================================249		ibdev:	(RO) Show Infiniband (IB) device name250 251		port:	(RO) Display port number252		======= =====================================253 254 255What:		/sys/class/infiniband_mad/abi_version256Date:		Apr, 2005257KernelVersion:	v2.6.12258Contact:	linux-rdma@vger.kernel.org259Description:260		(RO) Value is incremented if any changes are made that break261		userspace ABI compatibility of umad & issm devices.262 263 264What:		/sys/class/infiniband_verbs/uverbs<N>/ibdev265What:		/sys/class/infiniband_verbs/uverbs<N>/abi_version266Date:		Sept, 2005267KernelVersion:	v2.6.14268Contact:	linux-rdma@vger.kernel.org269Description:270		=============== ===========================================271		ibdev:		(RO) Display Infiniband (IB) device name272 273		abi_version:	(RO) Show ABI version of IB device specific274				interfaces.275		=============== ===========================================276 277 278What:		/sys/class/infiniband_verbs/abi_version279Date:		Sep, 2005280KernelVersion:	v2.6.14281Contact:	linux-rdma@vger.kernel.org282Description:283		(RO) Value is incremented if any changes are made that break284		userspace ABI compatibility of uverbs devices.285 286 287sysfs interface for Mellanox IB HCA low-level driver (mthca)288------------------------------------------------------------289 290What:		/sys/class/infiniband/mthcaX/hw_rev291What:		/sys/class/infiniband/mthcaX/hca_type292What:		/sys/class/infiniband/mthcaX/board_id293Date:		Apr, 2005294KernelVersion:	v2.6.12295Contact:	linux-rdma@vger.kernel.org296Description:297		=============== ================================================298		hw_rev:		(RO) Hardware revision number299 300		hca_type:	(RO) Host Channel Adapter type: MT23108, MT25208301				(MT23108 compat mode), MT25208 or MT25204302 303		board_id:	(RO) Manufacturing board ID304		=============== ================================================305 306 307sysfs interface for Mellanox ConnectX HCA IB driver (mlx4)308----------------------------------------------------------309 310What:		/sys/class/infiniband/mlx4_X/hw_rev311What:		/sys/class/infiniband/mlx4_X/hca_type312What:		/sys/class/infiniband/mlx4_X/board_id313Date:		Sep, 2007314KernelVersion:	v2.6.24315Contact:	linux-rdma@vger.kernel.org316Description:317		=============== ===============================318		hw_rev:		(RO) Hardware revision number319 320		hca_type:	(RO) Host channel adapter type321 322		board_id:	(RO) Manufacturing board ID323		=============== ===============================324 325 326What:		/sys/class/infiniband/mlx4_X/iov/ports/<port-num>/gids/<n>327What:		/sys/class/infiniband/mlx4_X/iov/ports/<port-num>/admin_guids/<n>328What:		/sys/class/infiniband/mlx4_X/iov/ports/<port-num>/pkeys/<n>329What:		/sys/class/infiniband/mlx4_X/iov/ports/<port-num>/mcgs/330What:		/sys/class/infiniband/mlx4_X/iov/ports/<pci-slot-num>/ports/<m>/gid_idx/0331What:		/sys/class/infiniband/mlx4_X/iov/ports/<pci-slot-num>/ports/<m>/pkey_idx/<n>332Date:		Aug, 2012333KernelVersion:	v3.6.15334Contact:	linux-rdma@vger.kernel.org335Description:336		The sysfs iov directory is used to manage and examine the port337		P_Key and guid paravirtualization. This directory is added only338		for the master -- slaves do not have it.339 340		Under iov/ports, the administrator may examine the gid and P_Key341		tables as they are present in the device (and as are seen in the342		"network view" presented to the SM).343 344		The "pkeys" and "gids" subdirectories contain one file for each345		entry in the port's P_Key or GID table respectively. For346		example, ports/1/pkeys/10 contains the value at index 10 in port347		1's P_Key table.348 349		======================= ==========================================350		gids/<n>:		(RO) The physical port gids n = 0..127351 352		admin_guids/<n>:	(RW) Allows examining or changing the353					administrative state of a given GUID354					n = 0..127355 356		pkeys/<n>:		(RO) Displays the contents of the physical357					key table n = 0..126358 359		mcgs/:			(RO) Multicast group table360 361		<m>/gid_idx/0:		(RO) Display the GID mapping m = 1..2362 363		<m>/pkey_idx/<n>:	(RW) Writable except for RoCE pkeys.364					m = 1..2, n = 0..126365 366					Under the iov/<pci slot number>367					directories, the admin may map the index368					numbers in the physical tables (as under369					iov/ports) to the paravirtualized index370					numbers that guests see.371 372					For example, if the administrator, for373					port 1 on guest 2 maps physical pkey374					index 10 to virtual index 1, then that375					guest, whenever it uses its pkey index376					1, will actually be using the real pkey377					index 10.378		======================= ==========================================379 380 381What:		/sys/class/infiniband/mlx4_X/iov/<pci-slot-num>/ports/<m>/smi_enabled382What:           /sys/class/infiniband/mlx4_X/iov/<pci-slot-num>/ports/<m>/enable_smi_admin383Date:		May, 2014384KernelVersion:	v3.15.7385Contact:	linux-rdma@vger.kernel.org386Description:387		Enabling QP0 on VFs for selected VF/port. By default, no VFs are388		enabled for QP0 operation.389 390		================= ==== ===========================================391		smi_enabled:	  (RO) Indicates whether smi is currently enabled392				       for the indicated VF/port393 394		enable_smi_admin: (RW) Used by the admin to request that smi395				       capability be enabled or disabled for the396				       indicated VF/port. 0 = disable, 1 = enable.397		================= ==== ===========================================398 399		The requested enablement will occur at the next reset of the VF400		(e.g. driver restart on the VM which owns the VF).401 402 403sysfs interface for Chelsio T4/T5 RDMA driver (cxgb4)404-----------------------------------------------------405 406What:		/sys/class/infiniband/cxgb4_X/hw_rev407What:		/sys/class/infiniband/cxgb4_X/hca_type408What:		/sys/class/infiniband/cxgb4_X/board_id409Date:		Apr, 2010410KernelVersion:	v2.6.35411Contact:	linux-rdma@vger.kernel.org412Description:413 414		=============== =============================================415		hw_rev:		(RO) Hardware revision number416 417		hca_type:	(RO) Driver short name. Should normally match418				the name in its bus driver structure (e.g.419				pci_driver::name)420 421		board_id:	(RO) Manufacturing board id. (Vendor + device422				information)423		=============== =============================================424 425 426sysfs interface for Intel IB driver qib427---------------------------------------428 429What:		/sys/class/infiniband/qibX/version430What:		/sys/class/infiniband/qibX/hw_rev431What:		/sys/class/infiniband/qibX/hca_type432What:		/sys/class/infiniband/qibX/board_id433What:		/sys/class/infiniband/qibX/boardversion434What:		/sys/class/infiniband/qibX/nctxts435What:		/sys/class/infiniband/qibX/localbus_info436What:		/sys/class/infiniband/qibX/tempsense437What:		/sys/class/infiniband/qibX/serial438What:		/sys/class/infiniband/qibX/nfreectxts439What:		/sys/class/infiniband/qibX/chip_reset440Date:		May, 2010441KernelVersion:	v2.6.35442Contact:	linux-rdma@vger.kernel.org443Description:444		=============== ======================================================445		version:	(RO) Display version information of installed software446				and drivers.447 448		hw_rev:		(RO) Hardware revision number449 450		hca_type:	(RO) Host channel adapter type451 452		board_id:	(RO) Manufacturing board id453 454		boardversion:	(RO) Current version of the chip architecture455 456		nctxts:		(RO) Return the number of user ports (contexts)457				available458 459		localbus_info:	(RO) Human readable localbus info460 461		tempsense:	(RO) Display temp sense registers in decimal462 463		serial:		(RO) Serial number of the HCA464 465		nfreectxts:	(RO) The number of free user ports (contexts)466				available.467 468		chip_reset:	(WO) Reset the chip if possible by writing469				"reset" to this file. Only allowed if no user470				contexts are open that use chip resources.471		=============== ======================================================472 473 474What:		/sys/class/infiniband/qibX/ports/<N>/sl2vl/[0-15]475Date:		May, 2010476KernelVersion:	v2.6.35477Contact:	linux-rdma@vger.kernel.org478Description:479		(RO) The directory contains 16 files numbered 0-15 that specify480		the Service Level (SL). Listing the SL files returns the Virtual481		Lane (VL) as programmed by the SL.482 483What:		/sys/class/infiniband/qibX/ports/<N>/CCMgtA/cc_settings_bin484What:		/sys/class/infiniband/qibX/ports/<N>/CCMgtA/cc_table_bin485Date:		May, 2010486KernelVersion:	v2.6.35487Contact:	linux-rdma@vger.kernel.org488Description:489		Per-port congestion control. Both are binary attributes.490 491		=============== ================================================492		cc_table_bin	(RO) Congestion control table size followed by493				table entries.494 495		cc_settings_bin (RO) Congestion settings: port control, control496				map and an array of 16 entries for the497				congestion entries - increase, timer, event log498				trigger threshold and the minimum injection rate499				delay.500		=============== ================================================501 502What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/loopback503What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/led_override504What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/hrtbt_enable505What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/status506What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/status_str507Date:		May, 2010508KernelVersion:	v2.6.35509Contact:	linux-rdma@vger.kernel.org510Description:511		[to be documented]512 513		=============== ===============================================514		loopback:	(WO)515		led_override:	(WO)516		hrtbt_enable:	(RW)517		status:		(RO)518 519		status_str:	(RO) Displays information about the link state,520				possible cable/switch problems, and hardware521				errors. Possible states are- "Initted",522				"Present", "IB_link_up", "IB_configured" or523				"Fatal_Hardware_Error".524		=============== ===============================================525 526What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rc_resends527What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/seq_naks528What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rdma_seq529What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rnr_naks530What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/other_naks531What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rc_timeouts532What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/look_pkts533What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/pkt_drops534What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/dma_wait535What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/unaligned536Date:		May, 2010537KernelVersion:	v2.6.35538Contact:	linux-rdma@vger.kernel.org539Description:540		[to be documented]541 542 543sysfs interface for Mellanox Connect-IB HCA driver mlx5544-------------------------------------------------------545 546What:		/sys/class/infiniband/mlx5_X/hw_rev547What:		/sys/class/infiniband/mlx5_X/hca_type548What:		/sys/class/infiniband/mlx5_X/reg_pages549What:		/sys/class/infiniband/mlx5_X/fw_pages550Date:		Jul, 2013551KernelVersion:	v3.11552Contact:	linux-rdma@vger.kernel.org553Description:554		[to be documented]555 556 557sysfs interface for Cisco VIC (usNIC) Verbs Driver558--------------------------------------------------559 560What:		/sys/class/infiniband/usnic_X/board_id561What:		/sys/class/infiniband/usnic_X/config562What:		/sys/class/infiniband/usnic_X/qp_per_vf563What:		/sys/class/infiniband/usnic_X/max_vf564What:		/sys/class/infiniband/usnic_X/cq_per_vf565What:		/sys/class/infiniband/usnic_X/iface566Date:		Sep, 2013567KernelVersion:	v3.14568Contact:	Christian Benvenuti <benve@cisco.com>,569		Dave Goodell <dgoodell@cisco.com>,570		linux-rdma@vger.kernel.org571Description:572 573		=============== ===============================================574		board_id:	(RO) Manufacturing board id575 576		config:		(RO) Report the configuration for this PF577 578		qp_per_vf:	(RO) Queue pairs per virtual function.579 580		max_vf:		(RO) Max virtual functions581 582		cq_per_vf:	(RO) Completion queue per virtual function583 584		iface:		(RO) Shows which network interface this usNIC585				entry is associated to (visible with ifconfig).586		=============== ===============================================587 588What:		/sys/class/infiniband/usnic_X/qpn/summary589What:		/sys/class/infiniband/usnic_X/qpn/context590Date:		Sep, 2013591KernelVersion:	v3.14592Contact:	Christian Benvenuti <benve@cisco.com>,593		Dave Goodell <dgoodell@cisco.com>,594		linux-rdma@vger.kernel.org595Description:596		[to be documented]597 598 599sysfs interface for Emulex RoCE HCA Driver600------------------------------------------601 602What:		/sys/class/infiniband/ocrdmaX/hw_rev603Date:		Feb, 2014604KernelVersion:	v3.14605Description:606		hw_rev:		(RO) Hardware revision number607 608What:		/sys/class/infiniband/ocrdmaX/hca_type609Date:		Jun, 2014610KernelVersion:	v3.16611Contact:	linux-rdma@vger.kernel.org612Description:613		hca_type:	(RO) Display FW version614 615 616sysfs interface for Intel Omni-Path driver (HFI1)617-------------------------------------------------618 619What:		/sys/class/infiniband/hfi1_X/hw_rev620What:		/sys/class/infiniband/hfi1_X/board_id621What:		/sys/class/infiniband/hfi1_X/nctxts622What:		/sys/class/infiniband/hfi1_X/serial623What:		/sys/class/infiniband/hfi1_X/chip_reset624What:		/sys/class/infiniband/hfi1_X/boardversion625What:		/sys/class/infiniband/hfi1_X/nfreectxts626What:		/sys/class/infiniband/hfi1_X/tempsense627Date:		May, 2016628KernelVersion:	v4.6629Contact:	linux-rdma@vger.kernel.org630Description:631		=============== =============================================632		hw_rev:		(RO) Hardware revision number633 634		board_id:	(RO) Manufacturing board id635 636		nctxts:		(RO) Total contexts available.637 638		serial:		(RO) Board serial number639 640		chip_reset:	(WO) Write "reset" to this file to reset the641				chip if possible. Only allowed if no user642				contexts are open that use chip resources.643 644		boardversion:	(RO) Human readable board info645 646		nfreectxts:	(RO) The number of free user ports (contexts)647				available.648 649		tempsense:	(RO) Thermal sense information650		=============== =============================================651 652 653What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_settings_bin654What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_table_bin655What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_prescan656Date:		May, 2016657KernelVersion:	v4.6658Contact:	linux-rdma@vger.kernel.org659Description:660		Per-port congestion control.661 662		=============== ================================================663		cc_table_bin	(RO) CCA tables used by PSM2 Congestion control664				table size followed by table entries. Binary665				attribute.666 667		cc_settings_bin (RO) Congestion settings: port control, control668				map and an array of 16 entries for the669				congestion entries - increase, timer, event log670				trigger threshold and the minimum injection rate671				delay. Binary attribute.672 673		cc_prescan	(RW) enable prescanning for faster BECN674				response. Write "on" to enable and "off" to675				disable.676		=============== ================================================677 678What:		/sys/class/infiniband/hfi1_X/ports/<N>/sc2vl/[0-31]679What:		/sys/class/infiniband/hfi1_X/ports/<N>/sl2sc/[0-31]680What:		/sys/class/infiniband/hfi1_X/ports/<N>/vl2mtu/[0-15]681Date:		May, 2016682KernelVersion:	v4.6683Contact:	linux-rdma@vger.kernel.org684Description:685		=============== ===================================================686		sc2vl/:		(RO) 32 files (0 - 31) used to translate sl->vl687 688		sl2sc/:		(RO) 32 files (0 - 31) used to translate sl->sc689 690		vl2mtu/:	(RO) 16 files (0 - 15) used to determine MTU for vl691		=============== ===================================================692 693 694What:		/sys/class/infiniband/hfi1_X/sdma_<N>/cpu_list695What:		/sys/class/infiniband/hfi1_X/sdma_<N>/vl696Date:		Sept, 2016697KernelVersion:	v4.8698Contact:	linux-rdma@vger.kernel.org699Description:700		sdma<N>/ contains one directory per sdma engine (0 - 15)701 702		=============== ==============================================703		cpu_list:	(RW) List of cpus for user-process to sdma704				engine assignment.705 706		vl:		(RO) Displays the virtual lane (vl) the sdma707				engine maps to.708		=============== ==============================================709 710		This interface gives the user control on the affinity settings711		for the device. As an example, to set an sdma engine irq712		affinity and thread affinity of a user processes to use the713		sdma engine, which is "near" in terms of NUMA configuration, or714		physical cpu location, the user will do::715 716		  echo "3" > /proc/irq/<N>/smp_affinity_list717		  echo "4-7" > /sys/devices/.../sdma3/cpu_list718		  cat /sys/devices/.../sdma3/vl719		  0720		  echo "8" > /proc/irq/<M>/smp_affinity_list721		  echo "9-12" > /sys/devices/.../sdma4/cpu_list722		  cat /sys/devices/.../sdma4/vl723		  1724 725		to make sure that when a process runs on cpus 4,5,6, or 7, and726		uses vl=0, then sdma engine 3 is selected by the driver, and727		also the interrupt of the sdma engine 3 is steered to cpu 3.728		Similarly, when a process runs on cpus 9,10,11, or 12 and sets729		vl=1, then engine 4 will be selected and the irq of the sdma730		engine 4 is steered to cpu 8.  This assumes that in the above N731		is the irq number of "sdma3", and M is irq number of "sdma4" in732		the /proc/interrupts file.733 734sysfs interface for QLogic qedr NIC Driver735------------------------------------------736 737What:		/sys/class/infiniband/qedrX/hw_rev738What:		/sys/class/infiniband/qedrX/hca_type739Date:		Oct, 2016740KernelVersion:	v4.10741Contact:	linux-rdma@vger.kernel.org742Description:743 744		=============== ==== ========================745		hw_rev:		(RO) Hardware revision number746 747		hca_type:	(RO) Display HCA type748		=============== ==== ========================749 750 751sysfs interface for VMware Paravirtual RDMA driver752--------------------------------------------------753 754What:		/sys/class/infiniband/vmw_pvrdmaX/hw_rev755What:		/sys/class/infiniband/vmw_pvrdmaX/hca_type756What:		/sys/class/infiniband/vmw_pvrdmaX/board_id757Date:		Oct, 2016758KernelVersion:	v4.10759Contact:	linux-rdma@vger.kernel.org760Description:761 762		=============== ==== =====================================763		hw_rev:		(RO) Hardware revision number764 765		hca_type:	(RO) Host channel adapter type766 767		board_id:	(RO) Display PVRDMA manufacturing board ID768		=============== ==== =====================================769 770 771sysfs interface for Broadcom NetXtreme-E RoCE driver772----------------------------------------------------773 774What:		/sys/class/infiniband/bnxt_reX/hw_rev775What:		/sys/class/infiniband/bnxt_reX/hca_type776Date:		Feb, 2017777KernelVersion:	v4.11778Contact:	linux-rdma@vger.kernel.org779Description:780		=============== ==== =========================781		hw_rev:		(RO) Hardware revision number782 783		hca_type:	(RO) Host channel adapter type784		=============== ==== =========================785