Pro Softnet Driver

Idrive.exe is a IDrive belonging to IDrive from Pro Softnet Corporation The “.exe” file extension stands for Windows executable file. Any program that is executable has the.exe file extension. IDrive Classic 6.7.1.46 download page. Download IDriveWinSetup.exe free. IDrive Classic Size: 25Mb. Downloaded: 1,649 times. This one crash was related to idrivewd600.exe is known as IDrive for Windows and it is developed by Pro Softnet Corporation. I cant find any English language info on it so I would remove it at least to test. Pro Softnet Corporation: iBackup Extractor.exe: iBackup Extractor: Wide Angle Software Ltd: iBackup Viewer.exe. Iball Baton 108m Wireless Pci Adapter Driver.exe. Remote Access Host is a program offered by the software company Pro Softnet Corp. Some people want to remove it. Sometimes this is hard because uninstalling this by hand requires some knowledge related to removing Windows applications by hand. The best QUICK approach to remove Remote Access Host is to use Advanced Uninstaller PRO.

Intel Gigabit Linux driver.Copyright(c) 1999 - 2013 Intel Corporation.

Contents¶

• Identifying Your Adapter
• Command Line Parameters
• Speed and Duplex Configuration
• Additional Configurations
• Support

Identifying Your Adapter¶

For more information on how to identify your adapter, go to the Adapter &Driver ID Guide at:

For the latest Intel network drivers for Linux, refer to the followingwebsite. In the search field, enter your adapter name or type, or use thenetworking link on the left to search for your adapter:

Command Line Parameters¶

The default value for each parameter is generally the recommended setting,unless otherwise noted.

For more information about the AutoNeg, Duplex, and Speedparameters, see the “Speed and Duplex Configuration” section inthis document.

For more information about the InterruptThrottleRate,RxIntDelay, TxIntDelay, RxAbsIntDelay, and TxAbsIntDelayparameters, see the application note at:http://www.intel.com/design/network/applnots/ap450.htm

AutoNeg¶

(Supported only on adapters with copper connections)

This parameter is a bit-mask that specifies the speed and duplex settingsadvertised by the adapter. When this parameter is used, the Speed andDuplex parameters must not be specified.

NOTE:

Refer to the Speed and Duplex section of this readme for moreinformation on the AutoNeg parameter.

Duplex¶

(Supported only on adapters with copper connections)

This defines the direction in which data is allowed to flow. Can beeither one or two-directional. If both Duplex and the link partner areset to auto-negotiate, the board auto-detects the correct duplex. If thelink partner is forced (either full or half), Duplex defaults to half-duplex.

FlowControl¶

This parameter controls the automatic generation(Tx) and response(Rx)to Ethernet PAUSE frames.

InterruptThrottleRate¶

(not supported on Intel(R) 82542, 82543 or 82544-based adapters)

The driver can limit the amount of interrupts per second that the adapterwill generate for incoming packets. It does this by writing a value to theadapter that is based on the maximum amount of interrupts that the adapterwill generate per second.

Setting InterruptThrottleRate to a value greater or equal to 100will program the adapter to send out a maximum of that many interruptsper second, even if more packets have come in. This reduces interruptload on the system and can lower CPU utilization under heavy load,but will increase latency as packets are not processed as quickly.

The default behaviour of the driver previously assumed a staticInterruptThrottleRate value of 8000, providing a good fallback value forall traffic types,but lacking in small packet performance and latency.The hardware can handle many more small packets per second however, andfor this reason an adaptive interrupt moderation algorithm was implemented.

Since 7.3.x, the driver has two adaptive modes (setting 1 or 3) in whichit dynamically adjusts the InterruptThrottleRate value based on the trafficthat it receives. After determining the type of incoming traffic in the lasttimeframe, it will adjust the InterruptThrottleRate to an appropriate valuefor that traffic.

The algorithm classifies the incoming traffic every interval intoclasses. Once the class is determined, the InterruptThrottleRate value isadjusted to suit that traffic type the best. There are three classes defined:“Bulk traffic”, for large amounts of packets of normal size; “Low latency”,for small amounts of traffic and/or a significant percentage of smallpackets; and “Lowest latency”, for almost completely small packets orminimal traffic.

In dynamic conservative mode, the InterruptThrottleRate value is set to 4000for traffic that falls in class “Bulk traffic”. If traffic falls in the “Lowlatency” or “Lowest latency” class, the InterruptThrottleRate is increasedstepwise to 20000. This default mode is suitable for most applications.

For situations where low latency is vital such as cluster orgrid computing, the algorithm can reduce latency even more whenInterruptThrottleRate is set to mode 1. In this mode, which operatesthe same as mode 3, the InterruptThrottleRate will be increased stepwise to70000 for traffic in class “Lowest latency”.

In simplified mode the interrupt rate is based on the ratio of TX andRX traffic. If the bytes per second rate is approximately equal, theinterrupt rate will drop as low as 2000 interrupts per second. If thetraffic is mostly transmit or mostly receive, the interrupt rate couldbe as high as 8000.

Setting InterruptThrottleRate to 0 turns off any interrupt moderationand may improve small packet latency, but is generally not suitablefor bulk throughput traffic.

When e1000 is loaded with default settings and multiple adaptersare in use simultaneously, the CPU utilization may increase non-linearly. In order to limit the CPU utilization without impactingthe overall throughput, we recommend that you load the driver asfollows:

This sets the InterruptThrottleRate to 3000 interrupts/sec forthe first, second, and third instances of the driver. The rangeof 2000 to 3000 interrupts per second works on a majority ofsystems and is a good starting point, but the optimal value willbe platform-specific. If CPU utilization is not a concern, useRX_POLLING (NAPI) and default driver settings.

RxDescriptors¶

This value specifies the number of receive buffer descriptors allocatedby the driver. Increasing this value allows the driver to buffer moreincoming packets, at the expense of increased system memory utilization.

Each descriptor is 16 bytes. A receive buffer is also allocated for eachdescriptor and can be either 2048, 4096, 8192, or 16384 bytes, dependingon the MTU setting. The maximum MTU size is 16110.

NOTE:

MTU designates the frame size. It only needs to be set for JumboFrames. Depending on the available system resources, the requestfor a higher number of receive descriptors may be denied. In thiscase, use a lower number.

RxIntDelay¶

This value delays the generation of receive interrupts in units of 1.024microseconds. Receive interrupt reduction can improve CPU efficiency ifproperly tuned for specific network traffic. Increasing this value addsextra latency to frame reception and can end up decreasing the throughputof TCP traffic. If the system is reporting dropped receives, this valuemay be set too high, causing the driver to run out of available receivedescriptors.

CAUTION:

When setting RxIntDelay to a value other than 0, adapters mayhang (stop transmitting) under certain network conditions. Ifthis occurs a NETDEV WATCHDOG message is logged in the systemevent log. In addition, the controller is automatically reset,restoring the network connection. To eliminate the potentialfor the hang ensure that RxIntDelay is set to 0.

RxAbsIntDelay¶

(This parameter is supported only on 82540, 82545 and later adapters.)

This value, in units of 1.024 microseconds, limits the delay in which areceive interrupt is generated. Useful only if RxIntDelay is non-zero,this value ensures that an interrupt is generated after the initialpacket is received within the set amount of time. Proper tuning,along with RxIntDelay, may improve traffic throughput in specific networkconditions.

Speed¶

(This parameter is supported only on adapters with copper connections.)

Pro Softnet Driver Installer

Speed forces the line speed to the specified value in megabits per second(Mbps). If this parameter is not specified or is set to 0 and the linkpartner is set to auto-negotiate, the board will auto-detect the correctspeed. Duplex should also be set when Speed is set to either 10 or 100.

TxDescriptors¶

Pro Softnet Driver Updater

This value is the number of transmit descriptors allocated by the driver.Increasing this value allows the driver to queue more transmits. Eachdescriptor is 16 bytes.

NOTE:

Depending on the available system resources, the request for ahigher number of transmit descriptors may be denied. In this case,use a lower number.

TxIntDelay¶

This value delays the generation of transmit interrupts in units of1.024 microseconds. Transmit interrupt reduction can improve CPUefficiency if properly tuned for specific network traffic. If thesystem is reporting dropped transmits, this value may be set too highcausing the driver to run out of available transmit descriptors.

TxAbsIntDelay¶

(This parameter is supported only on 82540, 82545 and later adapters.)

This value, in units of 1.024 microseconds, limits the delay in which atransmit interrupt is generated. Useful only if TxIntDelay is non-zero,this value ensures that an interrupt is generated after the initialpacket is sent on the wire within the set amount of time. Proper tuning,along with TxIntDelay, may improve traffic throughput in specificnetwork conditions.

Pro Softnet Idrive

XsumRX¶

(This parameter is NOT supported on the 82542-based adapter.)

A value of ‘1’ indicates that the driver should enable IP checksumoffload for received packets (both UDP and TCP) to the adapter hardware.

Copybreak¶

Driver copies all packets below or equaling this size to a fresh RXbuffer before handing it up the stack.

This parameter is different than other parameters, in that it is asingle (not 1,1,1 etc.) parameter applied to all driver instances andit is also available during runtime at/sys/module/e1000/parameters/copybreak

SmartPowerDownEnable¶

Allows PHY to turn off in lower power states. The user can turn offthis parameter in supported chipsets.

Speed and Duplex Configuration¶

Three keywords are used to control the speed and duplex configuration.These keywords are Speed, Duplex, and AutoNeg.

If the board uses a fiber interface, these keywords are ignored, and thefiber interface board only links at 1000 Mbps full-duplex.

For copper-based boards, the keywords interact as follows:

• The default operation is auto-negotiate. The board advertises allsupported speed and duplex combinations, and it links at the highestcommon speed and duplex mode IF the link partner is set to auto-negotiate.
• If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbpsis advertised (The 1000BaseT spec requires auto-negotiation.)
• If Speed = 10 or 100, then both Speed and Duplex should be set. Auto-negotiation is disabled, and the AutoNeg parameter is ignored. PartnerSHOULD also be forced.

The AutoNeg parameter is used when more control is required over theauto-negotiation process. It should be used when you wish to control whichspeed and duplex combinations are advertised during the auto-negotiationprocess.

The parameter may be specified as either a decimal or hexadecimal value asdetermined by the bitmap below.

Some examples of using AutoNeg:

Note that when this parameter is used, Speed and Duplex must not be specified.

Pro Softnet Drivers

If the link partner is forced to a specific speed and duplex, then thisparameter should not be used. Instead, use the Speed and Duplex parameterspreviously mentioned to force the adapter to the same speed and duplex.

Additional Configurations¶

Jumbo Frames¶

Jumbo Frames support is enabled by changing the MTU to a value larger thanthe default of 1500. Use the ifconfig command to increase the MTU size.For example:

This setting is not saved across reboots. It can be made permanent ifyou add:

to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This exampleapplies to the Red Hat distributions; other distributions may store thissetting in a different location.

Degradation in throughput performance may be observed in some Jumbo framesenvironments. If this is observed, increasing the application’s socket buffersize and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.See the specific application manual and /usr/src/linux*/Documentation/networking/ip-sysctl.txt for more details.

• The maximum MTU setting for Jumbo Frames is 16110. This value coincideswith the maximum Jumbo Frames size of 16128.

• Using Jumbo frames at 10 or 100 Mbps is not supported and may result inpoor performance or loss of link.

• Adapters based on the Intel(R) 82542 and 82573V/E controller do notsupport Jumbo Frames. These correspond to the following product names:

ethtool¶

The driver utilizes the ethtool interface for driver configuration anddiagnostics, as well as displaying statistical information. The ethtoolversion 1.6 or later is required for this functionality.

The latest release of ethtool can be found fromhttps://www.kernel.org/pub/software/network/ethtool/

Enabling Wake on LAN (WoL)¶

WoL is configured through the ethtool utility.

WoL will be enabled on the system during the next shut down or reboot.For this driver version, in order to enable WoL, the e1000 driver must beloaded when shutting down or rebooting the system.

Support¶

For general information, go to the Intel support website at:

or the Intel Wired Networking project hosted by Sourceforge at:

If an issue is identified with the released source code on the supportedkernel with a supported adapter, email the specific information relatedto the issue to e1000-devel@lists.sf.net