summaryrefslogtreecommitdiffstats
path: root/include/crypto
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2011-03-27 16:50:41 +0000
committerDavid S. Miller <davem@davemloft.net>2011-03-28 22:26:33 -0700
commitc211c9698920d2b114bd8fbf913c8bdab3918461 (patch)
tree825cecf620b74d5ffca3fe3ee615e4d907ae5152 /include/crypto
parenta715dea3c8e9ef2771c534e05ee1d36f65987e64 (diff)
downloadblackbird-op-linux-c211c9698920d2b114bd8fbf913c8bdab3918461.tar.gz
blackbird-op-linux-c211c9698920d2b114bd8fbf913c8bdab3918461.zip
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>
Diffstat (limited to 'include/crypto')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud