| commit | c211c9698920d2b114bd8fbf913c8bdab3918461 | |
| author | Anton Blanchard <anton@samba.org> | |
| Sun, 27 Mar 2011 16:50:41 +0000 (27 16:50 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Tue, 29 Mar 2011 05:26:33 +0000 (28 22:26 -0700) | ||
| tree | 825cecf620b74d5ffca3fe3ee615e4d907ae5152 | treesnapshot (tar.gz zip) |
| parent | a715dea3c8e9ef2771c534e05ee1d36f65987e64 | commitdiff |
cxgb3: Apply interrupt coalescing settings to all queues
While testing the performance of different receive interrupt
coalescing settings on a single stream TCP benchmark, I noticed two
very different results. With rx-usecs=50, most of the time a
connection would hit 8280 Mbps but once in a while it would hit
9330 Mbps.
It turns out we are only applying the interrupt coalescing settings
to the first queue and whenever the rx hash would direct us onto
that queue we ran faster.
With this patch applied and rx-usecs=50, I get 9330 Mbps
consistently.
Signed-off-by: Anton Blanchard <anton@samba.org>
Acked-by: Divy Le Ray <divy@chelsio.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
While testing the performance of different receive interrupt
coalescing settings on a single stream TCP benchmark, I noticed two
very different results. With rx-usecs=50, most of the time a
connection would hit 8280 Mbps but once in a while it would hit
9330 Mbps.
It turns out we are only applying the interrupt coalescing settings
to the first queue and whenever the rx hash would direct us onto
that queue we ran faster.
With this patch applied and rx-usecs=50, I get 9330 Mbps
consistently.
Signed-off-by: Anton Blanchard <anton@samba.org>
Acked-by: Divy Le Ray <divy@chelsio.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| drivers/net/cxgb3/cxgb3_main.c | diffblobblamehistory |