Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #641
Difficulty: Medium
NeXTSTEP had a Unix operating system based on the Minix kernel, plus source code from System V.
True or False?
Linux & Unix Commands - Search Man Pages

if_ntb(4) [freebsd man page]

NTB(4)							   BSD Kernel Interfaces Manual 						    NTB(4)

NAME
ntb, ntb_hw, if_ntb -- Intel(R) Non-Transparent Bridge driver SYNOPSIS
To compile this driver into your kernel, place the following lines in your kernel configuration file: device ntb_hw device if_ntb Or, to load the driver as a module at boot, place the following line in loader.conf(5): if_ntb_load="YES" DESCRIPTION
The ntb driver provides support for the Non-Transparent Bridge (NTB) in the Intel S1200, Xeon E3 and Xeon E5 processor families. The NTB allows you to connect two computer systems using a PCI-e link if they have the correct equipment and connectors. CONFIGURATION
The NTB memory windows need to be configured by the BIOS. If your BIOS allows you to set their size, you should set the size of both memory windows to 1 MiB. This needs to be done on both systems. Each system needs to have a different IP address assigned. The MAC address is randomly generated. Also for maximum performance, the MTU should be set to 16 kiB. This can be done by adding the line below to rc.conf(5): ifconfig_ntb0="inet 192.168.1.10 netmask 255.255.255.0 mtu 16384" And on the second system : ifconfig_ntb0="inet 192.168.1.11 netmask 255.255.255.0 mtu 16384" If you are using the UDP protocol, you may want to increase the net.inet.udp.maxdgram sysctl(8) variable. SEE ALSO
rc.conf(5), sysctl(8) AUTHORS
The ntb driver was developed by Intel and originally written by Carl Delsey <carl@FreeBSD.org>. BUGS
If the driver is unloaded, it cannot be reloaded without a system reboot. The network support is limited. It isn't fully configurable yet. It also isn't integrated into netgraph(4) or bpf(4). NTB to Root Port mode is not yet supported. There is no way to protect your system from malicious behavior on the other system once the link is brought up. Anyone with root or kernel access on the other system can read or write to any location on your system. In other words, only connect two systems that completely trust each other. BSD
Apr 11, 2013 BSD

Check Out this Related Man Page

MPS(4)							   BSD Kernel Interfaces Manual 						    MPS(4)

NAME
mps -- LSI Fusion-MPT 2 Serial Attached SCSI driver SYNOPSIS
To compile this driver into your kernel, place the following lines in your kernel configuration file: device scbus device mps Or, to load the driver as a module at boot, place the following line in loader.conf(5): mps_load="YES" DESCRIPTION
The mps driver provides support for LSI Logic Fusion-MPT 2 SAS controllers and WarpDrive solid state storage cards. HARDWARE
The mps driver supports the following hardware: o LSI Logic SAS2004 (4 Port SAS) o LSI Logic SAS2008 (8 Port SAS) o LSI Logic SAS2108 (8 Port SAS) o LSI Logic SAS2116 (16 Port SAS) o LSI Logic SAS2208 (8 Port SAS) o LSI Logic SAS2308 (8 Port SAS) o LSI Logic SSS6200 Solid State Storage o Intel Integrated RAID Module RMS25JB040 o Intel Integrated RAID Module RMS25JB080 o Intel Integrated RAID Module RMS25KB040 o Intel Integrated RAID Module RMS25KB080 CONFIGURATION
To disable MSI interrupts for all mps driver instances, set the following tunable value in loader.conf(5): hw.mps.disable_msi=1 To disable MSI interrupts for a specific mps driver instance, set the following tunable value in loader.conf(5): dev.mps.X.disable_msi=1 where X is the adapter number. To disable MSI-X interrupts for all mps driver instances, set the following tunable value in loader.conf(5): hw.mps.disable_msix=1 To disable MSI-X interrupts for a specific mps driver instance, set the following tunable value in loader.conf(5): dev.mps.X.disable_msix=1 To set the maximum number of DMA chains allocated for all adapters, set the following variable in loader.conf(5): hw.mps.max_chains=NNNN To set the maximum number of DMA chains allocated for a specific adapter, set the following variable in loader.conf(5): dev.mps.X.max_chains=NNNN This variable may also be viewed via sysctl(8) to see the maximum set for a given adapter. The current number of free chain frames may be seen via the dev.mps.X.chain_free sysctl(8) variable. The lowest number of free chain frames may be seen via the dev.mps.X.chain_free_lowwater sysctl(8) variable. The current number of active I/O commands is shown in the dev.mps.X.io_cmds_active sysctl(8) variable. The maximum number of active I/O command seen since boot is shown in the dev.mps.X.io_cmds_highwater sysctl(8) variable. DEBUGGING
To enable debugging prints from the mps driver, set the hw.mps.X.debug_level variable, where X is the adapter number, either in loader.conf(5) or via sysctl(8). The following bits have the described effects: 0x01 Enable informational prints. 0x02 Enable tracing prints. 0x04 Enable prints for driver faults. 0x08 Enable prints for controller events. SEE ALSO
cd(4), ch(4), da(4), mpt(4), pci(4), sa(4), scsi(4), targ(4), loader.conf(5), sysctl(8) HISTORY
The mps driver first appeared in FreeBSD 9.0. AUTHORS
The mps driver was originally written by Scott Long <scottl@FreeBSD.org>. It has been improved and tested by LSI Logic Corporation. This man page was written by Ken Merry <ken@FreeBSD.org>. BUGS
This driver has a couple of known shortcomings: o No userland utility available (e.g. mptutil(8)). o The driver probes devices sequentially. If your system has a large number of devices, the probe will take a while. BSD
January 3, 2013 BSD

Featured Tech Videos