TCP Offloading Never Works For Me

[Espionage724]

I am interesting in trying TCP Offloading, but I have yet to see visible proof that it ever worked.

Following the guide here tells me that in order to enable the feature, I have to enter

netsh int tcp set global chimney=enabled

in a (administrative) Command Prompt. Doing this gives me an Ok. and then I restart.


I have every offload option enabled in the device settings:


And netsh is reporting the option enabled (Chimney Offload State):


But every entry that appears when I type netstat -t is always InHost, never Offloaded


Anyone have any ideas as to what is wrong here? I'm on Windows 7 x64 SP1 with all updates.

[grunger]

To be honest in my general experience with TCP offloading and other features along the same lines, Recieve side scaling etc is that they are pretty hit and miss and often cause more problems than they solve.

Microsoft PSS recommend that these features are disabled generally, especially on servers (which is what I do)

I wouldn't worry too much about it and even if you do see it listed in netstat I don't think you'll see any real world difference to be honest.

[thatguy91]

NetDMA is under thing that you could enable for better performance and not have work for you

What version driver are you using?

EDIT: under thing? another thing!

[Corrupt^]

Originally Posted by grunger

To be honest in my general experience with TCP offloading and other features along the same lines, Recieve side scaling etc is that they are pretty hit and miss and often cause more problems than they

I've got one example right here:

"Packet loss in Source engine games"

Started up wireshark and eventually pinned it down to offloading. Turned off offloading and my packet loss was gone.

[thatguy91]

Things like NetDMA and Direct Cache Access should actually reduce package loss and ping times, although I doubt whether they're ever actually utilised features on standard boards.