Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

esh(4) [netbsd man page]

ESH(4)							   BSD Kernel Interfaces Manual 						    ESH(4)

NAME
esh -- RoadRunner-based HIPPI interfaces device driver SYNOPSIS
esh* at pci? dev ? function ? DESCRIPTION
The esh device driver supports the Essential Communications RoadRunner-based HIPPI interfaces. With some modifications, the driver could be made to support the Gigabit Ethernet card based on the same chip. The driver supports both a normal network interface and a raw HIPPI Framing Protocol (HIPPI-FP) device. The HIPPI-FP interface is accessed via the /dev/eshN/ulpN set of devices. There are 255 available Upper Layer Protocols in FP; these are selectable via the various device entries. HIPPI is an 800-megabit/sec networking technology which supports extremely large packet sizes. In order to efficiently use this network, the kernel should be configured with extra mbufs, and the default socket buffer size should be increased to at least 192KB, regardless of the expected bandwidth-delay product of the network. HIPPI ARP is not widely used, and the NetBSD stack does not support it (yet). In order to define the mappings between IP addresses and ifields (the HIPPI MAC addresses), the administrator must make link-layer entries in the routing table using the route(8) command: route add -interface 129.99.154.101 -llinfo -link esh0:3.0.0.65 MEDIA SELECTION
Media selection is not yet supported for this device. SEE ALSO
intro(4), pci(4), eshconfig(8), ifconfig(8), route(8) BUGS
The card must be tuned for proper and efficient DMA operation. The appropriate values vary based on the system. The eshconfig(8) program is used for this. BSD
January 28, 1998 BSD

Check Out this Related Man Page

ESHCONFIG(8)						    BSD System Manager's Manual 					      ESHCONFIG(8)

NAME
eshconfig -- configure Essential Communications' HIPPI network interface SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface] DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update that firmware. Available operands for eshconfig: -b bytes Adjust the burst size for read (by NIC of host memory) DMA. -c bytes Adjust the burst size for write (by NIC of host memory) DMA. -d filename Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every line, and a tag line at the end indicating the characteristics of the firmware file. -e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter ensures that the changes will be written to EEPROM. -i usecs Interrupt delay in microseconds. -m bytes Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents one direction from dominating the flow of bytes, and artificially throttling the NIC. -r bytes Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are requested, the DMA will not begin. -s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics. -t Show current tuning parameters on the host. -u filename Name of file to which the NIC firmware should be uploaded. Not currently supported. -w bytes Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will not start. -x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter- faces goes up and down. Only the super-user may modify the configuration of a network interface. DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration. SEE ALSO
esh(4), ifconfig(8) HISTORY
The eshconfig command first appeared in NetBSD 1.4. BSD
June 17, 2005 BSD
Man Page