summaryrefslogtreecommitdiff
path: root/net/bridge
diff options
context:
space:
mode:
authorstephen hemminger <shemminger@vyatta.com>2010-08-30 07:51:17 +0000
committerDavid S. Miller <davem@davemloft.net>2010-09-01 14:49:33 -0700
commitde6be6c1f77798c4da38301693d33aff1cd76e84 (patch)
treef00cedd75ddae577847cd334f099f3560fb5cced /net/bridge
parent750e9fad8c7f44e0005ffb7195f72dd76978c2cf (diff)
downloadlinux-3.10-de6be6c1f77798c4da38301693d33aff1cd76e84.tar.gz
linux-3.10-de6be6c1f77798c4da38301693d33aff1cd76e84.tar.bz2
linux-3.10-de6be6c1f77798c4da38301693d33aff1cd76e84.zip
sky2: don't do GRO on second port
There's something very important I forgot to tell you. What? Don't cross the GRO streams. Why? It would be bad. I'm fuzzy on the whole good/bad thing. What do you mean, "bad"? Try to imagine all the Internet as you know it stopping instantaneously and every bit in every packet swapping at the speed of light. Total packet reordering. Right. That's bad. Okay. All right. Important safety tip. Thanks, Hubert The simplest way to stop this is just avoid doing GRO on the second port. Very few Marvell boards support two ports per ring, and GRO is just an optimization. Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge')
0 files changed, 0 insertions, 0 deletions